linux-kernel - [PATCH 0/3] make KVM PV use apic through APIs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 15 Jul 2012 15:56:39 +0300
From:	"Michael S. Tsirkin" <mst@...hat.com>
To:	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
	Jacob Pan <jacob.jun.pan@...el.com>,
	Fernando Luis Vazquez Cao <fernando@....ntt.co.jp>,
	Suresh Siddha <suresh.b.siddha@...el.com>,
	Joerg Roedel <joerg.roedel@....com>,
	Yinghai Lu <yinghai@...nel.org>, linux-kernel@...r.kernel.org,
	kvm@...r.kernel.org, avi@...hat.com, gleb@...hat.com
Subject: [PATCH 0/3] make KVM PV use apic through APIs

KVM PV EOI optimization overrides eoi_write apic op with its own
version. at Ingo's suggestion, add an API for this and switch kvm to use
it, to avoid meddling with core x86 apic driver data structures
directly.

Ingo, could you please review and let us know whether this
matches what you had in mind?

This patchset is on top of kvm/next since it touches some
of the code modified in that tree (and patch 3 reverts a commit
in that tree). Could x86 some maintainers pls ACK merging this patchset
through the kvm tree?

Michael S. Tsirkin (3):
  apic: add apic_set_eoi_write for PV use
  kvm: switch to apic_set_eoi_write, apic_write
  Revert "apic: fix kvm build on UP without IOAPIC"

 arch/x86/include/asm/apic.h |  8 +++-----
 arch/x86/kernel/apic/apic.c | 17 +++++++++++++++++
 arch/x86/kernel/kvm.c       | 13 +++----------
 3 files changed, 23 insertions(+), 15 deletions(-)

-- 
MST
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/