All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Jan Beulich <jbeulich@novell.com>
Subject: Re: Illegal PV kernel pfm/pfn translations on PROT_NONE ioremaps
Date: Fri, 28 Mar 2008 16:44:55 +0000	[thread overview]
Message-ID: <C412D107.1E882%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <1206722470.17918.21.camel@sisko.scot.redhat.com>

On 28/3/08 16:41, "Stephen C. Tweedie" <sct@redhat.com> wrote:

>> ...and the issue is now fixed (changeset 488) in
>> http://xenbits.xensource.com/staging/linux-2.6.18-xen.hg
> 
> I've merged this for RHEL-5.2 (along with cset 492), and now have
> multiple reports that it has fixed the X crashes --- thanks!
> 
> We'll need to keep it queued for pvops, too, as that is going to need
> the whole PROT_NONE special handling in order to support migrate.  I'm
> away all next week, I'll have to deal with it when I get back.

Great. You also need c/s 492, unless you already fixed the i386 non-PAE
build breakage that c/s 488 introduces.

 -- Keir

  reply	other threads:[~2008-03-28 16:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-19 15:39 Illegal PV kernel pfm/pfn translations on PROT_NONE ioremaps Stephen C. Tweedie
2008-03-19 16:00 ` Keir Fraser
2008-03-19 16:31   ` Stephen C. Tweedie
2008-03-19 16:42     ` Keir Fraser
2008-03-19 17:12       ` Stephen C. Tweedie
2008-03-19 18:52         ` Keir Fraser
2008-03-20 11:39           ` Keir Fraser
2008-03-28 16:41             ` Stephen C. Tweedie
2008-03-28 16:44               ` Keir Fraser [this message]
2008-03-28 16:45                 ` Keir Fraser
2008-03-19 16:34   ` Keir Fraser

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=C412D107.1E882%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=jbeulich@novell.com \
    --cc=jeremy@goop.org \
    --cc=sct@redhat.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.