From: ebiederm@xmission.com (Eric W. Biederman)
To: Bernhard Walle <bernhard@bwalle.de>
Cc: Simon Horman <horms@verge.net.au>,
Kexec Mailing List <kexec@lists.infradead.org>
Subject: Re: [PATCH 0/3] Getting biarch support
Date: Thu, 11 Mar 2010 00:35:14 -0800 [thread overview]
Message-ID: <m1ociv9ry5.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <20100311092240.21222nl5qlr5mou8@webmail.df.eu> (Bernhard Walle's message of "Thu\, 11 Mar 2010 09\:22\:40 +0100")
Bernhard Walle <bernhard@bwalle.de> writes:
> Zitat von "Eric W. Biederman" <ebiederm@xmission.com>:
>
>>
>> It looks like no one ever tested taking a crashdump
>> from a 64bit kernel with a 32bit userspace on x86,
>> and we have a reuse-cmdline regression fixes follow.
>
> I didn't even know that it is supposed to work...
The x86 biarch tends to be an after thought. But we
have to do the hard work for all of the architectures
where the optimal configuration is 32bit userspace with
a 64bit kernel. So we might as well have it work on
x86 so we can test the code without need an exotic
architecture.
In my case it was purely code size savings on an embedded
setup that got me using, and thus fixing it.
Eric
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2010-03-11 8:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 8:16 [PATCH 0/3] Getting biarch support Eric W. Biederman
2010-03-11 8:20 ` [PATCH 1/3] Refix concat_cmdline Eric W. Biederman
2010-03-11 8:20 ` [PATCH 0/3] Getting biarch support Simon Horman
2010-03-11 8:21 ` [PATCH 2/3] kexec: Figure out our native architecture before load Eric W. Biederman
2010-03-11 8:22 ` [PATCH 3/3] x86: Fix biarch crashdump setup Eric W. Biederman
2010-03-11 8:22 ` [PATCH 0/3] Getting biarch support Bernhard Walle
2010-03-11 8:35 ` Eric W. Biederman [this message]
2010-03-11 8:48 ` Simon Horman
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=m1ociv9ry5.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=bernhard@bwalle.de \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
/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