From: Laszlo Ersek <lersek@redhat.com>
To: Dennis Luehring <dl.soluz@gmx.net>,
Richard Henderson <rth@twiddle.net>,
Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"Richard W.M. Jones" <rjones@redhat.com>
Subject: Re: [Qemu-devel] alpha platform is missing files after initrd load
Date: Mon, 7 Nov 2016 15:15:54 +0100 [thread overview]
Message-ID: <c0afa265-a434-e085-7dfa-3999b2962663@redhat.com> (raw)
In-Reply-To: <b7e3f3a7-be1b-ad0c-947b-5cf4b2f63976@gmx.net>
On 11/07/16 08:35, Dennis Luehring wrote:
> Am 04.11.2016 um 20:40 schrieb Laszlo Ersek:
>> I guess it is "possible to design a system which can recover from
>> this", except noone seems to have bothered, since 2009. (Ditto for the
>> proposed "panic-level=X" alternative.)
>>
>> I've now briefly considered posting a trivial kernel patch for this,
>> but having learned about the above commit, I don't think so...
>
> i tried to get some response on the linux-kernel or initramfs
> mailinglist 1-2 weeks ago but no one seems to care
>
> but i still think it would help alot to if some more known developers
> would get involved and send in a patch for this - if only for starting a
> discussion about the
>
> situation
>
Please report the issue directly to the author of commit 73310a169aeb,
that is, "H. Peter Anvin" <hpa@zytor.com> (the latter is his current
email address). Please identify the commit to him and feel free to
reference this discussion on qemu-devel, using the mailing list archive.
If Peter still believes the current logic is valid, no work (= patch)
will have been in vain. If Peter agrees the current logic is wrong after
all, then he should be able to write a patch for you that he won't
dislike (so several iterations won't be necessary for the patch).
Thanks
Laszlo
next prev parent reply other threads:[~2016-11-07 14:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 10:45 [Qemu-devel] alpha platform is missing files after initrd load Dennis Luehring
2016-11-04 11:08 ` Stefan Hajnoczi
2016-11-04 16:37 ` Richard Henderson
2016-11-04 19:40 ` Laszlo Ersek
2016-11-04 21:08 ` Richard Henderson
2016-11-07 7:37 ` Dennis Luehring
2016-11-07 14:12 ` Laszlo Ersek
2016-11-07 14:38 ` Dennis Luehring
2016-11-07 15:56 ` Laszlo Ersek
2016-11-07 16:11 ` Dennis Luehring
2016-11-07 17:21 ` Laszlo Ersek
2016-11-09 6:34 ` Dennis Luehring
2016-11-11 6:49 ` Dennis Luehring
2016-11-07 7:35 ` Dennis Luehring
2016-11-07 14:15 ` Laszlo Ersek [this message]
2016-11-07 14:18 ` Laszlo Ersek
2016-11-07 15:16 ` Dennis Luehring
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=c0afa265-a434-e085-7dfa-3999b2962663@redhat.com \
--to=lersek@redhat.com \
--cc=dl.soluz@gmx.net \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
--cc=rth@twiddle.net \
--cc=stefanha@gmail.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.