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-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 06 Oct 2010 10:31:03 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Stefano Stabellini <stefano.stabellini@...citrix.com>,
	Thomas Gleixner <tglx@...utronix.de>
CC:	x86@...nel.org, linux-kernel@...r.kernel.org,
	xen-devel@...ts.xensource.com, "jeremy@...p.org" <jeremy@...p.org>,
	"konrad.wilk@...cle.com" <konrad.wilk@...cle.com>
Subject: Re: [PATCH 4/7] acpi: use indirect call to register gsi in different
 modes

On 10/06/2010 10:00 AM, Stefano Stabellini wrote:
> Peter,
> I sent this patch a while back as part of the "PV on HVM: receive
> interrupts as xen events" series (that it is based upon Konrad's
> pcifront series, he sent another version to the list yesterday).
> 
> Do you think that this is a reasonble approach?
> 
> If you want to give a look at the whole series you can find it here:
> 
> http://lkml.org/lkml/2010/8/30/170
> 
> everything else is Xen specific stuff.
> 
> Thanks in advance,
> 

On the surface it seems reasonable.

Thomas Gleixner has been working on greatly revamping a bunch of the x86
interrupt code, and this might interact with his stuff, so it would be
good if he could comment on it.

[tglx: what they're apparently working on is to redirect APIC interrupts
to Xen event channels so they don't have to interact with the simulated
memory-mapped APIC.  It's "paravirtualization light".]


-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ