From: "H. Peter Anvin" <hpa@zytor.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Guenter Roeck <guenter.roeck@ericsson.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: [PATCH v3] x86: Do not write into VGA memory space if there is no VGA device in the system
Date: Mon, 26 Apr 2010 07:52:39 -0700 [thread overview]
Message-ID: <4BD5A8B7.4050208@zytor.com> (raw)
In-Reply-To: <j2l84144f021004260735ib574b5f1t6c00a3a8a8f886ee@mail.gmail.com>
On 04/26/2010 07:35 AM, Pekka Enberg wrote:
>>>
>>> Wouldn't it be better to switch to, say, serial console here to avoid
>>> the NULL check in early_printk()?
>>>
>> This would be another possibility.
>>
>> However, since the serial console was not explicitly selected, it would possibly
>> not be initialized. My understanding is that Peter had a problem with that.
>>
>> One can argue that it would still be better to select the serial console in that case,
>> even though it might not be initialized. Actually, most likely it is (if it exists),
>> since the system must presumably have some means to communicate with the world.
>>
>> I am pretty much open to either option, if that results in the patch being accepted.
>> Just let me know which way to go.
>
> Peter?
Yes, I really don't want to issue bytes to a serial port that isn't
known to be initialized; it could take a *very* long time even if the
port is actually present, and if the port *isn't* present it could hang
the kernel.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2010-04-26 14:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 16:16 [PATCH v3] x86: Do not write into VGA memory space if there is no VGA device in the system Guenter Roeck
2010-04-26 9:36 ` Pekka Enberg
2010-04-26 14:05 ` Guenter Roeck
2010-04-26 14:35 ` Pekka Enberg
2010-04-26 14:52 ` H. Peter Anvin [this message]
2010-04-26 15:43 ` Bastien ROUCARIES
2010-04-26 16:11 ` Guenter Roeck
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=4BD5A8B7.4050208@zytor.com \
--to=hpa@zytor.com \
--cc=guenter.roeck@ericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=penberg@cs.helsinki.fi \
--cc=x86@kernel.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