From: Ian Campbell <ijc@hellion.org.uk>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Sally-Anne Edwards <sallyanne.edwards@googlemail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Fwd: domU lenny not working: BUG: unable to handle kernel paging request at e7437cc0
Date: Mon, 25 Aug 2008 21:54:32 +0100 [thread overview]
Message-ID: <1219697672.27921.178.camel@localhost.localdomain> (raw)
In-Reply-To: <48B31522.2050101@goop.org>
[-- Attachment #1: Type: text/plain, Size: 767 bytes --]
On Mon, 2008-08-25 at 13:25 -0700, Jeremy Fitzhardinge wrote:
> Ian Campbell wrote:
> > On Mon, 2008-08-25 at 20:46 +0100, Ian Campbell wrote:
> >
> >> I thought the tools did this (so expected the Lenny tools to be
> >> correct) but looking at the code it seems it is the domain 0 kernel
> >> which does it.
> >>
> >
> > Uh, I'm thinking backwards here. It's the frontend which writes it but
> > the backend needs to understand it which the Etch kernel does not.
> >
>
> Should we push that patch back into stable kernels?
The pvops kernel frontend already does the right thing. I'll look into
what it would take to get the support added to the backends in Etch.
Ian.
--
Ian Campbell
Matrimony isn't a word, it's a sentence.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-08-25 20:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <39fd98ca0808240801x7edbe0e6gf242f08de88cd92c@mail.gmail.com>
2008-08-24 15:04 ` Sally-Anne Edwards
2008-08-25 19:35 ` Jeremy Fitzhardinge
2008-08-25 19:46 ` Ian Campbell
2008-08-25 20:22 ` Ian Campbell
2008-08-25 20:25 ` Jeremy Fitzhardinge
2008-08-25 20:54 ` Ian Campbell [this message]
2008-08-25 20:59 ` Jeremy Fitzhardinge
2008-08-26 6:06 ` Ian Campbell
2008-08-25 19:56 ` Sally-Anne Edwards
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=1219697672.27921.178.camel@localhost.localdomain \
--to=ijc@hellion.org.uk \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sallyanne.edwards@googlemail.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
all inboxes | Powered by JetHome®