All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@novell.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>,
	Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: Re: Xen's use of PAT and PV guests
Date: Wed, 31 Mar 2010 09:26:19 +0100	[thread overview]
Message-ID: <4BB3234B0200007800038153@vpn.id2.novell.com> (raw)
In-Reply-To: <4BB2463A.9090401@goop.org>

>>> Jeremy Fitzhardinge <jeremy@goop.org> 30.03.10 20:43 >>>
>On 03/30/2010 09:57 AM, Konrad Rzeszutek Wilk wrote:
>> How does this work on pages shared across domains? Say Guest A makes the
>> page WC,Dom0 makes it WB and Xen puts it in WC, and Dom0 reads does a
>> Write/Read/Write, but in actuallity it is a Read/Write/Write. Or is
>> there no danger there since the grant table pages have UC set on them?
>>    
>
>Not sure.  That would invoke undefined behaviour, I'd assume.  Does Xen 
>keep track of memory type aliases?  Grant pages don't have to be UC do 
>they?  Pages between front and backends don't need to be (and shouldn't 
>be) UC.

Granted pages are RAM pages, and hence should always be WB
everywhere.

As to Xen's memory type handling - iirc the most recent memory type
used in a page table entry determines what Xen uses in its 1:1 mapping,
but I don't think global consistency is being enforced.

Jan

  reply	other threads:[~2010-03-31  8:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-30  0:35 Xen's use of PAT and PV guests Jeremy Fitzhardinge
2010-03-30  7:44 ` Jan Beulich
2010-03-30 17:39   ` Jeremy Fitzhardinge
2010-03-30 17:59     ` Keir Fraser
2010-03-30 18:25       ` Jeremy Fitzhardinge
2010-03-30 16:57 ` Konrad Rzeszutek Wilk
2010-03-30 18:43   ` Jeremy Fitzhardinge
2010-03-31  8:26     ` Jan Beulich [this message]
2010-03-30 17:56 ` Ian Campbell
2010-03-30 21:47   ` Jeremy Fitzhardinge
2010-03-31  8:31     ` Ian Campbell
2010-03-31 16:55       ` Jeremy Fitzhardinge

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=4BB3234B0200007800038153@vpn.id2.novell.com \
    --to=jbeulich@novell.com \
    --cc=jeremy@goop.org \
    --cc=keir.fraser@eu.citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=xen-devel@lists.xensource.com \
    /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.