The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Adrian Bunk <bunk@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	the arch/x86 maintainers <x86@kernel.org>,
	Rusty Russell <rusty@rustcorp.com.au>,
	chrisw@sous-sol.org, xen-devel@lists.xensource.com
Subject: Re: [git pull] xen, x86 fixes
Date: Tue, 24 Jun 2008 08:40:55 -0400	[thread overview]
Message-ID: <4860EB57.30402@goop.org> (raw)
In-Reply-To: <20080624073847.GA1897@cs181140183.pp.htv.fi>

Adrian Bunk wrote:
> Another compile error from the x86 tree:
>
> <--  snip  -->
>
> ...
>   CC      arch/x86/xen/mmu.o
> /home/bunk/linux/kernel-2.6/git/linux-2.6/arch/x86/xen/mmu.c: In function ‘xen_pmd_val’:
> /home/bunk/linux/kernel-2.6/git/linux-2.6/arch/x86/xen/mmu.c:229: error: ‘pmd_t’ has no member named ‘pmd’
> make[2]: *** [arch/x86/xen/mmu.o] Error 1
>
> <--  snip  -->
>
> The problem seems to be related to CONFIG_X86_PAE=n which results in
> PAGETABLE_LEVELS == 2.
>
> Not visible in -next due to "xen: remove support for non-PAE 32-bit",
> but that is not in 2.6.26.
>   

Thanks Adrian,

Bringing that patch over into .26 would be the easiest fix.  It's 
effectively a bugfix because non-PAE Xen is broken and unusable anyway.

Alternatively, I can easily put a little patch together to use the right 
accessors that will compile in non-PAE.

    J

  reply	other threads:[~2008-06-24 12:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-23 19:40 [git pull] xen, x86 fixes Ingo Molnar
2008-06-24  7:38 ` Adrian Bunk
2008-06-24 12:40   ` Jeremy Fitzhardinge [this message]
2008-06-24 15:18     ` Ingo Molnar

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=4860EB57.30402@goop.org \
    --to=jeremy@goop.org \
    --cc=bunk@kernel.org \
    --cc=chrisw@sous-sol.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rusty@rustcorp.com.au \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.org \
    --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