1. 08 9月, 2016 1 次提交
    • M
      arm64: KVM: vgic-v2: Add the GICV emulation infrastructure · fb5ee369
      Marc Zyngier 提交于
      In order to efficiently perform the GICV access on behalf of the
      guest, we need to be able to avoid going back all the way to
      the host kernel.
      
      For this, we introduce a new hook in the world switch code,
      conveniently placed just after populating the fault info.
      At that point, we only have saved/restored the GP registers,
      and we can quickly perform all the required checks (data abort,
      translation fault, valid faulting syndrome, not an external
      abort, not a PTW).
      
      Coming back from the emulation code, we need to skip the emulated
      instruction. This involves an additional bit of save/restore in
      order to be able to access the guest's PC (and possibly CPSR if
      this is a 32bit guest).
      
      At this stage, no emulation code is provided.
      Signed-off-by: NMarc Zyngier <marc.zyngier@arm.com>
      Reviewed-by: NChristoffer Dall <christoffer.dall@linaro.org>
      Signed-off-by: NChristoffer Dall <christoffer.dall@linaro.org>
      fb5ee369
  2. 04 7月, 2016 2 次提交
  3. 29 3月, 2016 1 次提交
  4. 01 3月, 2016 6 次提交
  5. 14 12月, 2015 11 次提交
  6. 30 4月, 2014 2 次提交
  7. 12 6月, 2013 1 次提交
  8. 24 1月, 2013 1 次提交
  9. 17 9月, 2012 4 次提交
  10. 18 7月, 2007 1 次提交
  11. 19 6月, 2006 1 次提交
  12. 10 1月, 2006 2 次提交
  13. 16 11月, 2005 1 次提交
  14. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4