From: Daniel Stodden <daniel.stodden@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: dom0 pvops crash
Date: Sun, 7 Feb 2010 14:22:15 -0800 [thread overview]
Message-ID: <1265581335.658.2.camel@agari.van.xensource.com> (raw)
In-Reply-To: <1265578978.2938.3.camel@localhost.localdomain>
On Sun, 2010-02-07 at 16:42 -0500, Ian Campbell wrote:
> On Sun, 2010-02-07 at 19:35 +0000, Pasi Kärkkäinen wrote:
> > On Wed, Jan 27, 2010 at 05:26:13PM +0000, Ian Campbell wrote:
> > > diff --git a/arch/x86/mm/pgtable.c b/arch/x86/mm/pgtable.c
> > > index 65215ab..49f8e83 100644
> > > --- a/arch/x86/mm/pgtable.c
> > > +++ b/arch/x86/mm/pgtable.c
> > > @@ -28,7 +28,10 @@ pgtable_t pte_alloc_one(struct mm_struct *mm, unsigned long address)
> > > struct page *pte;
> > >
> > > #ifdef CONFIG_HIGHPTE
> > > - pte = alloc_pages(PGALLOC_GFP | __GFP_HIGHMEM, 0);
> > > + if (is_xen_domain())
> > > + pte = alloc_pages(PGALLOC_GFP, 0);
> > > + else
> > > + pte = alloc_pages(PGALLOC_GFP | __GFP_HIGHMEM, 0);
> > > #else
> > > pte = alloc_pages(PGALLOC_GFP, 0);
> > > #endif
> > >
> >
> > I just tried this patch, but it fails to compile:
> >
> > arch/x86/mm/pgtable.c: In function 'pte_alloc_one':
> > arch/x86/mm/pgtable.c:19: error: implicit declaration of function 'is_xen_domain'
> > make[2]: *** [arch/x86/mm/pgtable.o] Error 1
> > make[1]: *** [arch/x86/mm] Error 2
> > make: *** [arch/x86] Error 2
> >
> > I tried grepping around for that function but didn't find it from any header..
>
> IIRC on some kernels it was called just xen_domain(), I'm not sure but I
> think my patch was against plain 2.6.32. I think the function (whatever
> it is called) also moved around in the headers recently.
is_running_on_xen()
Daniel
next prev parent reply other threads:[~2010-02-07 22:22 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 16:29 dom0 pvops crash Ian Jackson
2010-01-25 17:10 ` Keir Fraser
2010-01-25 17:28 ` Ian Jackson
2010-01-25 17:54 ` Pasi Kärkkäinen
2010-01-25 18:03 ` Ian Jackson
2010-01-25 18:57 ` Keir Fraser
2010-01-25 19:00 ` Jeremy Fitzhardinge
2010-01-25 19:31 ` Keir Fraser
2010-01-25 20:02 ` Jeremy Fitzhardinge
2010-01-26 11:53 ` Jan Beulich
2010-01-27 17:26 ` Ian Campbell
2010-01-27 18:50 ` Jeremy Fitzhardinge
2010-01-27 19:18 ` Ian Campbell
2010-01-27 19:34 ` Jeremy Fitzhardinge
2010-01-27 20:03 ` Pasi Kärkkäinen
2010-01-27 20:07 ` Jeremy Fitzhardinge
2010-02-07 19:35 ` Pasi Kärkkäinen
2010-02-07 21:42 ` Ian Campbell
2010-02-07 22:22 ` Daniel Stodden [this message]
2010-02-08 7:41 ` Pasi Kärkkäinen
2010-02-08 7:47 ` Ian Campbell
2010-02-08 8:06 ` Pasi Kärkkäinen
2010-02-08 8:50 ` Ian Campbell
2010-02-08 8:57 ` Pasi Kärkkäinen
2010-02-08 12:57 ` Xen pvops kernel CONFIG_HIGHPTE race/crash Pasi Kärkkäinen
2010-02-08 17:34 ` Pasi Kärkkäinen
2010-02-09 9:14 ` Ian Campbell
2010-01-25 18:18 ` dom0 pvops crash Ian Pratt
2010-01-25 18:26 ` Ian Campbell
2010-02-02 10:23 ` Pasi Kärkkäinen
2010-02-02 10:31 ` Ian Campbell
2010-02-02 10:45 ` Pasi Kärkkäinen
2010-01-25 17:11 ` Pasi Kärkkäinen
2010-01-25 17:30 ` Ian Jackson
2010-01-25 17:42 ` Pasi Kärkkäinen
2010-01-26 13:45 ` Ian Jackson
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=1265581335.658.2.camel@agari.van.xensource.com \
--to=daniel.stodden@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Keir.Fraser@eu.citrix.com \
--cc=jeremy@goop.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 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.