[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20080115013409.GB7969@verge.net.au>
Date: Tue, 15 Jan 2008 10:34:10 +0900
From: Simon Horman <horms@...ge.net.au>
To: Ian Campbell <Ian.Campbell@...rix.com>
Cc: Vivek Goyal <vgoyal@...hat.com>,
"Huang, Ying" <ying.huang@...el.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, Magnus Damm <magnus.damm@...il.com>
Subject: Re: [PATCH -mm 1/2] kexec/i386: kexec page table code clean up -
add arch_kimage
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists