[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Is: axe read_tscp pvops call. Was: Re: [RFC] ACPI S3 and Xen (suprisingly small\!).

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
From: "H. Peter Anvin" <hpa@xxxxxxxxx>
Date: Wed, 17 Oct 2012 09:54:12 -0700
Cc: linux-acpi@xxxxxxxxxxxxxxx, x86@xxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, lenb@xxxxxxxxxx
Delivery-date: Wed, 17 Oct 2012 16:54:32 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

On 10/17/2012 09:39 AM, Konrad Rzeszutek Wilk wrote:


which implies that it since it is a vDSO area it cannot do paravirt
calls anyhow.


Obviously.  The vdso is *user space*.

        -hpa

--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

References:
- [Xen-devel] [RFC] ACPI S3 and Xen (suprisingly small\!).
  - From: Konrad Rzeszutek Wilk
- Re: [Xen-devel] [RFC] ACPI S3 and Xen (suprisingly small\!).
  - From: H. Peter Anvin
- [Xen-devel] Is: axe read_tscp pvops call. Was: Re: [RFC] ACPI S3 and Xen (suprisingly small\!).
  - From: Konrad Rzeszutek Wilk
- Re: [Xen-devel] Is: axe read_tscp pvops call. Was: Re: [RFC] ACPI S3 and Xen (suprisingly small\!).
  - From: Konrad Rzeszutek Wilk

Prev by Date: Re: [Xen-devel] Is: axe read_tscp pvops call. Was: Re: [RFC] ACPI S3 and Xen (suprisingly small\!).
Next by Date: [Xen-devel] [RFC PATCH] paravirt: Remove paravirt_rdtscp as all platforms use the native version anyhow.
Previous by thread: Re: [Xen-devel] Is: axe read_tscp pvops call. Was: Re: [RFC] ACPI S3 and Xen (suprisingly small\!).
Next by thread: Re: [Xen-devel] [RFC] ACPI S3 and Xen (suprisingly small\!).
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.