[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130126182114.GA26786@aepfle.de>
Date: Sat, 26 Jan 2013 19:21:15 +0100
From: Olaf Hering <olaf@...fle.de>
To: KY Srinivasan <kys@...rosoft.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Greg KH <gregkh@...uxfoundation.org>,
"Jan Beulich (JBeulich@...e.com)" <JBeulich@...e.com>
Subject: Re: [PATCH] x86: Hyper-V: register clocksource only if its advertised
On Sat, Jan 26, KY Srinivasan wrote:
>
>
> > -----Original Message-----
> > From: Olaf Hering [mailto:olaf@...fle.de]
> > Sent: Friday, January 25, 2013 3:00 PM
> > To: KY Srinivasan
> > Cc: linux-kernel@...r.kernel.org; Greg KH; Jan Beulich (JBeulich@...e.com)
> > Subject: Re: [PATCH] x86: Hyper-V: register clocksource only if its advertised
> >
> > On Fri, Jan 25, KY Srinivasan wrote:
> >
> > > Your current approach of using the "Partition Reference Counter"
> > > feature bit is very fragile. Let us assume that future Windows guests
> > > depend on this feature; Xen would certainly emulate this to have a
> > > "good" emulation of Hyper-V and we are back to square one.
> >
> > If Xen starts to emulate the "Partition Reference Counter" feature,
> > wouldnt it also advertise this feature?
>
> Olaf, did you get a chance to investigate why the viridian bit was set
> for the Linux HVM domain.
I dont know, most likely XenServer sets this per default?
> I am thinking of re-sending the patch for delivering the Hyper-V vmbus
> on a separate vector without a run-time check. Let me know.
Are you also acking/nacking this patch?
Olaf
--
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