xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Josip Rodin <joy@entuzijast.net>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: __supported_pte_mask |= _PAGE_IOMAP twice?
Date: Sun, 22 Aug 2010 14:07:05 +0100	[thread overview]
Message-ID: <1282482425.11348.892.camel@localhost.localdomain> (raw)
In-Reply-To: <20100822120636.GA32564@entuzijast.net>

On Sun, 2010-08-22 at 13:06 +0100, Josip Rodin wrote:
> Hi,
> 
> I don't really understand this, but in xen-2.6.36/dom0/core there's this:
> 
> % git diff 0c2b1aa4c31830d3b9a40061d1b5f6c8cd837d57 057e5006127460b11e03bf80227881c528b0590d
> diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c
> index 167ca78..0850bd6 100644
> --- a/arch/x86/xen/enlighten.c
> +++ b/arch/x86/xen/enlighten.c
> @@ -1195,12 +1195,12 @@ asmlinkage void __init xen_start_kernel(void)
>  
>         pgd = (pgd_t *)xen_start_info->pt_base;
>  
> -       if (xen_initial_domain())
> -               __supported_pte_mask |= _PAGE_IOMAP;
> -       else
> +       if (!xen_initial_domain())
>                 __supported_pte_mask &= ~(_PAGE_PWT | _PAGE_PCD);
>  
>         __supported_pte_mask |= _PAGE_IOMAP;
> +
> +       __supported_pte_mask |= _PAGE_IOMAP;
>         /* Don't do the full vcpu_info placement stuff until we have a
>            possible map and a non-dummy shared_info. */
>         per_cpu(xen_vcpu, 0) = &HYPERVISOR_shared_info->vcpu_info[0];
> 
> 
> What's the point of doing the same thing twice at the end? Maybe it's
> a mis-merge?

Yes, I think its a mismerge. The same thing was in xen/stable-2.6.32.x
until recently as well.

Ian.

      parent reply	other threads:[~2010-08-22 13:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-22 12:06 __supported_pte_mask |= _PAGE_IOMAP twice? Josip Rodin
2010-08-22 12:13 ` Josip Rodin
2010-08-22 13:07 ` Ian Campbell [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=1282482425.11348.892.camel@localhost.localdomain \
    --to=ian.campbell@citrix.com \
    --cc=joy@entuzijast.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).