All of lore.kernel.org
 help / color / mirror / Atom feed
From: josh-iaAMLnmF4UmaiuxdJuQwMA@public.gmane.org
To: Peter Jones <pjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Matt Fleming
	<matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH] Don't print an error on unsupported BGRT version.
Date: Wed, 22 Jul 2015 11:23:08 -0700	[thread overview]
Message-ID: <20150722182308.GA26620@cloud> (raw)
In-Reply-To: <20150722170906.GA17419-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

On Wed, Jul 22, 2015 at 01:09:06PM -0400, Peter Jones wrote:
> On Wed, Jul 22, 2015 at 09:53:57AM -0700, Josh Triplett wrote:
> > On Wed, Jul 22, 2015 at 12:40:53PM -0400, Peter Jones wrote:
> > > BGRT can legitimately be a different version from what we support, and
> > > that's a problem with the driver not supporting something, not an error
> > > that needs to be surfaced to the user.
> > > 
> > > Signed-off-by: Peter Jones <pjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> > 
> > Are you actually seeing this error on a real system?  Or is this just a
> > theoretical concern with some future version?
> 
> Yeah, I have several systems where I see it every boot - and with
> "quiet", it's the only message I see.  In all cases the version is 0,
> i.e. the code was written before it was included in the standard, and
> it's a version the driver legitimately does not handle.  Admittedly
> these are mostly machines for developing UEFI on (including the Intel
> S1200RP board with the UDK2014 B2 firmware.)  But the fact is there are
> systems you can *buy* which will show this as an error, and it really
> isn't an error.  It's just an earlier version than we support.

We should support version 0.  Is the structure layout and semantic the
same?  Could you submit a patch to handle version 0?

> > While I agree that this doesn't need to be pr_err, I don't think
> > pr_debug is appropriate either.  It may mean the driver needs updating,
> > or it may mean that a system in the wild is actually broken and has an
> > invalid version number.  I'd prefer at least pr_warn so that people see
> > it and report it, but I could live with pr_notice; that should hide it
> > from systems booting in quiet mode, while still having it in the log
> > even on non-debug kernels.
> 
> I'd be okay with pr_notice.  I'll send a follow-up.

If we can handle 0, I'd prefer to do that and then have a pr_warn for
versions other than 0 and 1.

- Josh Triplett

  parent reply	other threads:[~2015-07-22 18:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-22 16:40 [PATCH] Don't print an error on unsupported BGRT version Peter Jones
     [not found] ` <1437583253-29600-1-git-send-email-pjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-07-22 16:53   ` Josh Triplett
2015-07-22 17:09     ` Peter Jones
     [not found]       ` <20150722170906.GA17419-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-07-22 18:23         ` josh-iaAMLnmF4UmaiuxdJuQwMA [this message]
2015-07-22 17:09     ` Peter Jones
2015-07-22 17:13     ` Peter Jones
     [not found]       ` <1437585207-32516-1-git-send-email-pjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-07-22 18:26         ` josh-iaAMLnmF4UmaiuxdJuQwMA
2015-07-22 22:13           ` Peter Jones

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=20150722182308.GA26620@cloud \
    --to=josh-iaamlnmf4umaiuxdjuqwma@public.gmane.org \
    --cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=pjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.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 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.