mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Guenter Roeck <guenter.roeck@ericsson.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>
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 17:35:16 +0300	[thread overview]
Message-ID: <j2l84144f021004260735ib574b5f1t6c00a3a8a8f886ee@mail.gmail.com> (raw)
In-Reply-To: <20100426140535.GA17135@ericsson.com>

On Mon, Apr 26, 2010 at 5:05 PM, Guenter Roeck
<guenter.roeck@ericsson.com> wrote:
> On Mon, Apr 26, 2010 at 05:36:05AM -0400, Pekka Enberg wrote:
>> Guenter Roeck kirjoitti:
>> > Ensure that early_printk() does not write into VGA memory space
>> > if there is not VGA device in the system.
>> >
>> > Signed-off-by: Guenter Roeck <guenter.roeck@ericsson.com>
>> > ---
>> > v3:
>> > Changes are now limited to early_printk.c. Functionality is retained, meaning
>> > there will still be output on the VGA console before setup_early_printk()
>> > is called, but only if a VGA device is known to exist in the system.
>> >
>> >  arch/x86/kernel/early_printk.c |   17 +++++++++++++----
>> >  1 files changed, 13 insertions(+), 4 deletions(-)
>> >
>> > diff --git a/arch/x86/kernel/early_printk.c b/arch/x86/kernel/early_printk.c
>> > index b9c830c..783cb25 100644
>> > --- a/arch/x86/kernel/early_printk.c
>> > +++ b/arch/x86/kernel/early_printk.c
>> > @@ -170,10 +170,13 @@ asmlinkage void early_printk(const char *fmt, ...)
>> >     int n;
>> >     va_list ap;
>> >
>> > -   va_start(ap, fmt);
>> > -   n = vscnprintf(buf, sizeof(buf), fmt, ap);
>> > -   early_console->write(early_console, buf, n);
>> > -   va_end(ap);
>> > +   if (early_console && (early_console_initialized ||
>> > +                         boot_params.screen_info.orig_video_isVGA == 1)) {
>> > +           va_start(ap, fmt);
>> > +           n = vscnprintf(buf, sizeof(buf), fmt, ap);
>> > +           early_console->write(early_console, buf, n);
>> > +           va_end(ap);
>> > +   }
>> >  }
>> >
>> >  static inline void early_console_register(struct console *con, int keep_early)
>> > @@ -233,6 +236,12 @@ static int __init setup_early_printk(char *buf)
>> >  #endif
>> >             buf++;
>> >     }
>> > +
>> > +   /* If there is no VGA device, don't try to use it as early console. */
>> > +   if (early_console == &early_vga_console &&
>> > +       boot_params.screen_info.orig_video_isVGA != 1)
>> > +           early_console = NULL;
>>
>> 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?

  reply	other threads:[~2010-04-26 14:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-20 16:16 Guenter Roeck
2010-04-26  9:36 ` Pekka Enberg
2010-04-26 14:05   ` Guenter Roeck
2010-04-26 14:35     ` Pekka Enberg [this message]
2010-04-26 14:52       ` H. Peter Anvin
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=j2l84144f021004260735ib574b5f1t6c00a3a8a8f886ee@mail.gmail.com \
    --to=penberg@cs.helsinki.fi \
    --cc=guenter.roeck@ericsson.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --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

all inboxes | Powered by JetHome®