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]
Message-ID: <alpine.DEB.2.00.1003041155590.24752@kaball-desktop>
Date:	Thu, 4 Mar 2010 11:58:35 +0000
From:	Stefano Stabellini <stefano.stabellini@...citrix.com>
To:	Sheng Yang <sheng@...ux.intel.com>
CC:	Jeremy Fitzhardinge <jeremy@...p.org>,
	Keir Fraser <Keir.Fraser@...citrix.com>,
	Jeremy Fitzhardinge <Jeremy.Fitzhardinge@...rix.com>,
	Ian Pratt <Ian.Pratt@...citrix.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	xen-devel <xen-devel@...ts.xensource.com>,
	Ian Campbell <Ian.Campbell@...citrix.com>,
	Stefano Stabellini <Stefano.Stabellini@...citrix.com>
Subject: Re: [Xen-devel] [PATCH 5/7] xen: Make event channel work with PV
 extension of HVM

On Thu, 4 Mar 2010, Sheng Yang wrote:
> On Tuesday 02 March 2010 09:38:21 Jeremy Fitzhardinge wrote:
> > On 03/01/2010 01:38 AM, Sheng Yang wrote:
> > > +
> > > +		x86_platform.calibrate_tsc = xen_tsc_khz;
> > > +		x86_platform.get_wallclock = xen_get_wallclock;
> > > +		x86_platform.set_wallclock = xen_set_wallclock;
> > > +
> > > +		pv_apic_ops = xen_apic_ops;
> > > +#ifdef CONFIG_X86_LOCAL_APIC
> > > +		/*
> > > +		 * set up the basic apic ops.
> > > +		 */
> > > +		set_xen_basic_apic_ops();
> > > +		apic->write = xen_hvm_pv_evtchn_apic_write;
> > 
> > I'd just change the xen_apic_write to remove the WARN_ON, since you
> > don't seem to care about it either.
> 
> So which code base I should make these patches against? We expect the patchset 
> can be accepted in the Linux upstream soon after you pick it up.

I think that once we agree on which approach we take we should work
together on this.

Jeremy, can we have our own temporary branch so that we can work
together on a common code base to finish this patch series?

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