This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-devel] RE: Solaris and PVRDTSCP

To: Keir Fraser <keir.xen@xxxxxxxxx>, Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] RE: Solaris and PVRDTSCP
From: Paul Durrant <Paul.Durrant@xxxxxxxxxx>
Date: Fri, 1 Jul 2011 20:33:19 +0100
Accept-language: en-US
Acceptlanguage: en-US
Delivery-date: Fri, 01 Jul 2011 12:34:06 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <CA33CAB0.1D5E3%keir.xen@xxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <512de115-3a6b-4957-8a6d-93dc724503eb@default> <CA33CAB0.1D5E3%keir.xen@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acw4GUpfiBeThPO/4kaVQshZwlq8HAADE7Qg
Thread-topic: [Xen-devel] RE: Solaris and PVRDTSCP
Cool. I'll go with the simple approach for now then :-)


> -----Original Message-----
> From: Keir Fraser [mailto:keir.xen@xxxxxxxxx]
> Sent: 01 July 2011 19:04
> To: Dan Magenheimer; Paul Durrant; xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] RE: Solaris and PVRDTSCP
> On 01/07/2011 18:51, "Dan Magenheimer" <dan.magenheimer@xxxxxxxxxx>
> wrote:
> >>   Clearly future versions of the Solaris kernel should revise
> this
> >> check but to allow this kernel to enable PV drivers I was
> wondering
> >> what sort of workaround could be done. My current thoughts are
> along
> >> the lines of disabling the extra CPUID leaf if tsc_mode is <
> >
> > This seems reasonable.  The info on that leaf could be useful in
> other
> > modes, but likely hasn't been.
> Tbh I'm fine with this as well, on the understanding that it may end
> up having to be fixed the hard way (explicit max_leaf) if we add
> anything more to the hypervisor cpuid space.
>  -- Keir

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>