From: Jeremy Fitzhardinge <jeremy@goop.org>
To: M A Young <m.a.young@durham.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: Tracebacks from dom0 pvops changeset 2342
Date: Mon, 09 Feb 2009 14:49:36 -0800 [thread overview]
Message-ID: <4990B300.9060302@goop.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0902092145560.14685@vega1.dur.ac.uk>
M A Young wrote:
> I tried again with the genuine changeset 2342 (2350 won't build for
> me, I get the error
> arch/x86/kernel/early_printk.c: In function 'early_dbgp_init':
> arch/x86/kernel/early_printk.c:827: error: 'PAGE_KERNEL_NOCACHE'
> undeclared (first use in this function)
> arch/x86/kernel/early_printk.c:827: error: (Each undeclared identifier
> is reported only once
> arch/x86/kernel/early_printk.c:827: error: for each function it
> appears in.)
> ) and the resulting dmesg is essentially the same, but without the pte
> related tracebacks, so the first two are still there.
Erm, yes. The x86-unify-* block of patches is a bit problematic; I
probably should have left them commented out. If you remove/comment out
them all, then it should build OK.
BTW, I'm in the middle of migrating this patch queue into git, which
will then be the official home for all Xen/pvops work. It should be
ready in the next day or so.
J
next prev parent reply other threads:[~2009-02-09 22:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-08 22:40 Tracebacks from dom0 pvops changeset 2342 M A Young
2009-02-09 1:39 ` Jeremy Fitzhardinge
2009-02-09 8:39 ` M A Young
2009-02-09 18:24 ` Jeremy Fitzhardinge
2009-02-09 18:57 ` M A Young
2009-02-09 19:37 ` Jeremy Fitzhardinge
2009-02-09 21:49 ` M A Young
2009-02-09 22:49 ` Jeremy Fitzhardinge [this message]
2009-02-10 0:45 ` Nakajima, Jun
2009-02-10 1:16 ` Jeremy Fitzhardinge
2009-02-12 5:55 ` Nakajima, Jun
2009-02-20 22:34 ` Jeremy Fitzhardinge
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=4990B300.9060302@goop.org \
--to=jeremy@goop.org \
--cc=m.a.young@durham.ac.uk \
--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.