All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] x86: convert BUG_ON()s to WARN_ON()s in read_descriptor()
Date: Fri, 16 Dec 2011 14:48:49 +0000	[thread overview]
Message-ID: <CB110AD1.27676%keir.xen@gmail.com> (raw)
In-Reply-To: <4EEB676102000078000687FA@nat28.tlf.novell.com>

On 16/12/2011 14:44, "Jan Beulich" <JBeulich@suse.com> wrote:

>>>> On 16.12.11 at 10:09, Keir Fraser <keir.xen@gmail.com> wrote:
>> On 15/12/2011 10:25, "Jan Beulich" <JBeulich@suse.com> wrote:
>> 
>>> In the light of AMD erratum #700, and given that these checks happen
>>> for debugging purposes only and also only in debug builds of the
>>> hypervisor, make the failures non-fatal.
>> 
>> I think the changeset comment should have a brief description of erratum
>> #700.
> 
> I'd do this, but ...
> 
>> I also some reference should be made in a comment above the first
>> WARN_ON, explaining why they are now WARN_Ons (again, with reference to #700
>> and its symptoms).
> 
> ... I now think that these should never have been BUG_ON()s in the
> first place (despite probably having been the one who introduced
> them).
> 
> Additionally, on a second look, check_descriptor() would not allow any
> of the affected selector types to be installed into a descriptor table,
> and we clearly don't put in any such descriptors ourselves, so from the
> perspective of the erratum we're okay without the patch.
> 
> So if you prefer them to stay BUG_ON(), I think I'll just withdraw the
> patch.

If the erratum cannot affect us then they may as well stay as BUG_ON and we
sidestep the whole thing.

 -- Keir

> Jan
> 
>> Apart from that:
>> Acked-by: Keir Fraser <keir@xen.org>
>> 
>>> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>>> 
>>> --- a/xen/arch/x86/traps.c
>>> +++ b/xen/arch/x86/traps.c
>>> @@ -1544,11 +1544,11 @@ static int read_descriptor(unsigned int
>>>              asm volatile (
>>>                  "larl %2,%0 ; setz %1"
>>>                  : "=r" (a), "=qm" (valid) : "rm" (sel));
>>> -            BUG_ON(valid && ((a & 0x00f0ff00) != *ar));
>>> +            WARN_ON(valid && ((a & 0x00f0ff00) != *ar));
>>>              asm volatile (
>>>                  "lsll %2,%0 ; setz %1"
>>>                  : "=r" (l), "=qm" (valid) : "rm" (sel));
>>> -            BUG_ON(valid && (l != *limit));
>>> +            WARN_ON(valid && (l != *limit));
>>>          }
>>>  #endif
>>>      }
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xensource.com
>>> http://lists.xensource.com/xen-devel
> 
> 
> 

  reply	other threads:[~2011-12-16 14:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-15 10:25 [PATCH] x86: convert BUG_ON()s to WARN_ON()s in read_descriptor() Jan Beulich
2011-12-15 12:36 ` Keir Fraser
2011-12-15 13:06   ` Jan Beulich
2011-12-15 13:10     ` Keir Fraser
2011-12-16  9:09 ` Keir Fraser
2011-12-16 14:44   ` Jan Beulich
2011-12-16 14:48     ` Keir Fraser [this message]
2011-12-16 17:59       ` Wei Huang

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=CB110AD1.27676%keir.xen@gmail.com \
    --to=keir.xen@gmail.com \
    --cc=JBeulich@suse.com \
    --cc=xen-devel@lists.xensource.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.