All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: xen-devel mailing list <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] Add new location of Linux direct-map to the places to look for writable mappings
Date: Fri, 12 Sep 2008 16:49:47 -0700	[thread overview]
Message-ID: <48CB001B.9040305@goop.org> (raw)
In-Reply-To: <de76405a0809120838kee79064s6e81254a6ad0ebce@mail.gmail.com>

George Dunlap wrote:
> Add new location of Linux direct-map to the places to look for
> writable mappings.
>
> Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com>
>
> diff -r dbac9ee4d761 xen/arch/x86/mm/shadow/common.c
> --- a/xen/arch/x86/mm/shadow/common.c	Mon Sep 08 16:02:13 2008 +0100
> +++ b/xen/arch/x86/mm/shadow/common.c	Fri Sep 12 16:42:32 2008 +0100
> @@ -2385,9 +2385,11 @@ int sh_remove_write_access(struct vcpu *
>                            + ((fault_addr & VADDR_MASK) >> 27), 3); break;
>              }
>
> -            /* 64bit Linux direct map at 0xffff810000000000; older kernels
> -             * had it at 0x0000010000000000UL */
> +            /* 64bit Linux direct map at 0xffff880000000000; older kernels
> +             * had it at 0xffff880000000000, and older kernels yet had it
>   

Should be "older kernels had it at 0xffff810000000000".

    J

      parent reply	other threads:[~2008-09-12 23:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-12 15:38 [PATCH] Add new location of Linux direct-map to the places to look for writable mappings George Dunlap
2008-09-12 15:57 ` Daniel Magenheimer
2008-09-12 19:19   ` [PATCH] Add new location of Linux direct-map to theplaces " Ian Pratt
2008-09-12 20:32     ` Gianluca Guida
2008-09-15  8:31     ` Tim Deegan
2008-09-15 10:56     ` George Dunlap
2008-09-12 23:49 ` Jeremy Fitzhardinge [this message]

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=48CB001B.9040305@goop.org \
    --to=jeremy@goop.org \
    --cc=George.Dunlap@eu.citrix.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.