From: Olaf Hering <olaf@aepfle.de>
To: KY Srinivasan <kys@microsoft.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
"Jan Beulich (JBeulich@suse.com)" <JBeulich@suse.com>
Subject: Re: [PATCH] x86: Hyper-V: register clocksource only if its advertised
Date: Sat, 26 Jan 2013 19:21:15 +0100 [thread overview]
Message-ID: <20130126182114.GA26786@aepfle.de> (raw)
In-Reply-To: <050ad0e312b54ff3af424c7128144a4d@SN2PR03MB061.namprd03.prod.outlook.com>
On Sat, Jan 26, KY Srinivasan wrote:
>
>
> > -----Original Message-----
> > From: Olaf Hering [mailto:olaf@aepfle.de]
> > Sent: Friday, January 25, 2013 3:00 PM
> > To: KY Srinivasan
> > Cc: linux-kernel@vger.kernel.org; Greg KH; Jan Beulich (JBeulich@suse.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
next prev parent reply other threads:[~2013-01-26 18:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 13:37 [PATCH] x86: Hyper-V: register clocksource only if its advertised Olaf Hering
2013-01-25 16:10 ` Greg KH
2013-01-25 16:43 ` KY Srinivasan
2013-01-25 16:54 ` Olaf Hering
2013-01-25 17:04 ` KY Srinivasan
2013-01-25 17:19 ` Olaf Hering
2013-01-25 17:39 ` KY Srinivasan
2013-01-25 20:00 ` Olaf Hering
2013-01-25 20:03 ` KY Srinivasan
2013-01-26 16:57 ` KY Srinivasan
2013-01-26 18:21 ` Olaf Hering [this message]
2013-01-28 17:44 ` Stefano Stabellini
2013-01-29 8:35 ` Jan Beulich
2013-01-29 9:26 ` Olaf Hering
2013-01-29 14:32 ` KY Srinivasan
2013-01-29 15:30 ` Stefano Stabellini
2013-01-29 15:58 ` KY Srinivasan
2013-01-29 16:14 ` Stefano Stabellini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130126182114.GA26786@aepfle.de \
--to=olaf@aepfle.de \
--cc=JBeulich@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.