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  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 9 Mar 2010 10:22:31 +0000
From:	Stefano Stabellini <stefano.stabellini@...citrix.com>
To:	Ian Campbell <Ian.Campbell@...citrix.com>
CC:	Jeremy Fitzhardinge <jeremy@...p.org>,
	Sheng Yang <sheng@...ux.intel.com>,
	Stefano Stabellini <Stefano.Stabellini@...citrix.com>,
	xen-devel <xen-devel@...ts.xensource.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Ian Pratt <Ian.Pratt@...citrix.com>,
	Jeremy Fitzhardinge <Jeremy.Fitzhardinge@...rix.com>,
	Keir Fraser <Keir.Fraser@...citrix.com>,
	Ingo Molnar <mingo@...e.hu>,
	Konrad Rzeszutek Wilk <kliw@...nok.org>
Subject: Re: [Xen-devel] [PATCH 7/7] xen: Enable event channel of PV extension
 of HVM

On Tue, 9 Mar 2010, Ian Campbell wrote:
> On Tue, 2010-03-09 at 07:00 +0000, Jeremy Fitzhardinge wrote:
> > On 03/08/2010 05:53 PM, Sheng Yang wrote:
> > > On Tuesday 09 March 2010 01:10:56 Stefano Stabellini wrote:
> > >    
> > >> I think that mapping interrupts into VIRQs is a bad idea: you should map
> > >> interrupts into pirqs instead, the code exists already on the kernel
> > >> side so we don't need to do any (ugly) change ther.
> > >>      
> > > The code existed in the pv_ops dom0 side, but not in the upstream Linux. The
> > > latter is our target. We want this work to be accepted by upstream Linux soon.
> 
> >    2. It has significant overlaps with the current xen.git development
> >       which is also targeted for upstream.  There's no point in creating
> >       an unnecessary duplicate mechanism when the infrastructure will be
> >       in place anyway.
> 
> There's also nothing stopping us from upstreaming portions of the "dom0"
> patchset ahead of full dom0 support if it is useful for some domU
> feature.
> 

Indeed.
You just need the pirq mappings and few other things, it shouldn't be
too hard.
At this point I am going to do that myself after this patch series is
completed.

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