From: Simon Horman <horms@verge.net.au>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Vivek Goyal <vgoyal@redhat.com>,
"Huang, Ying" <ying.huang@intel.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Magnus Damm <magnus.damm@gmail.com>
Subject: Re: [PATCH -mm 1/2] kexec/i386: kexec page table code clean up - add arch_kimage
Date: Tue, 15 Jan 2008 10:34:10 +0900 [thread overview]
Message-ID: <20080115013409.GB7969@verge.net.au> (raw)
In-Reply-To: <1200317376.11020.9.camel@localhost.localdomain>
On Mon, Jan 14, 2008 at 01:29:36PM +0000, Ian Campbell wrote:
>
> On Thu, 2008-01-10 at 17:15 +0900, Simon Horman wrote:
> > > Have you tested Xen too? Does it run into issues with this change?
> >
> > Xen will need to be updated for this change but it shouldn't be a big
> > deal. Basically right now it calls __ma() (which is kind of like __pa())
> > on kexec_pgd and friends. Updating the arguments to __ma() to use
> > the new arch_kimage pointers should be easy enough.
>
> I think you mean the Xen specific parts of the kexec machinery in the
> kernel.c would need updating rather than the hypervisor, right?
Yes, that is right. Sorry for the confusion.
> I don't think these changes will cause anything more than minor problems
> for whoever ports the Xen kexec stuff upstream.
>
> > N.B: As this is Dom0 code (not DomU) it is maintained in the xen
> > repository and has been merged into Linux.
>
> I don't think we would bother backporting these changes to there, would
> we?
No, I was more thinking of the situation where Xen moves its kernel forwards.
--
Horms
prev parent reply other threads:[~2008-01-15 1:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 2:57 Huang, Ying
2008-01-10 1:14 ` Vivek Goyal
2008-01-10 2:06 ` Huang, Ying
2008-01-10 8:15 ` Simon Horman
2008-01-14 13:29 ` Ian Campbell
2008-01-15 1:34 ` Simon Horman [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=20080115013409.GB7969@verge.net.au \
--to=horms@verge.net.au \
--cc=Ian.Campbell@citrix.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=vgoyal@redhat.com \
--cc=ying.huang@intel.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®