1. 11 5月, 2016 1 次提交
  2. 11 12月, 2015 1 次提交
  3. 10 10月, 2015 3 次提交
  4. 29 9月, 2015 1 次提交
  5. 27 8月, 2015 1 次提交
    • M
      irqchip/GICv3: Convert to EOImode == 1 · 0b6a3da9
      Marc Zyngier 提交于
      So far, GICv3 has been used in with EOImode == 0. The effect of this
      mode is to perform the priority drop and the deactivation of the
      interrupt at the same time.
      
      While this works perfectly for Linux (we only have a single priority),
      it causes issues when an interrupt is forwarded to a guest, and when
      we want the guest to perform the EOI itself.
      
      For this case, the GIC architecture provides EOImode == 1, where:
      - A write to ICC_EOIR1_EL1 drops the priority of the interrupt and
        leaves it active. Other interrupts at the same priority level can
        now be taken, but the active interrupt cannot be taken again
      - A write to ICC_DIR_EL1 marks the interrupt as inactive, meaning
        it can now be taken again.
      
      This patch converts the driver to be able to use this new mode,
      depending on whether or not the kernel can behave as a hypervisor.
      No feature change.
      Signed-off-by: NMarc Zyngier <marc.zyngier@arm.com>
      Reviewed-and-tested-by: NEric Auger <eric.auger@linaro.org>
      Cc: Christoffer Dall <christoffer.dall@linaro.org>
      Cc: Jiang Liu <jiang.liu@linux.intel.com>
      Cc: <linux-arm-kernel@lists.infradead.org>
      Cc: kvmarm@lists.cs.columbia.edu
      Cc: Jason Cooper <jason@lakedaemon.net>
      Link: http://lkml.kernel.org/r/1440604845-28229-2-git-send-email-marc.zyngier@arm.comSigned-off-by: NThomas Gleixner <tglx@linutronix.de>
      0b6a3da9
  6. 12 8月, 2015 1 次提交
  7. 30 7月, 2015 2 次提交
  8. 30 3月, 2015 2 次提交
  9. 08 3月, 2015 2 次提交
  10. 21 1月, 2015 2 次提交
  11. 26 11月, 2014 4 次提交
  12. 25 7月, 2014 1 次提交
  13. 09 7月, 2014 1 次提交