All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Sander Eikelenboom <linux@eikelenboom.it>
Cc: Jan Beulich <jbeulich@suse.com>, xen-devel@lists.xen.org
Subject: Re: Xen-unstable: Bisected Host boot failure on AMD Phenom
Date: Thu, 2 Mar 2017 20:02:04 +0000	[thread overview]
Message-ID: <fd340e81-8aca-e933-8591-2690a20ba360@citrix.com> (raw)
In-Reply-To: <0ff276c6-4603-8ba2-fc6c-60f8853ed421@oracle.com>

On 02/03/17 19:33, Boris Ostrovsky wrote:
>> I expect it might have something to do with fact that this failure to
>> boot is a 6-core system, rather than a power of two, at which point I
>> doubt the APIC IDs follow a linear trend.
>>
>> (Properly fixing the reported topology is going to be a can of worms. 
>> All this series is trying to do is use just enough duct-tape to get the
>> hypervisor into a state where we can sensibly fix the reported topology.)
>
> I think we are using the same duct-tape roll on the Linux side.

Really? I'm sure I have used several rolls already ;p

> For example,
>
> cc272163ea55 ("x86/xen: Fix APIC id mismatch warning on Intel")
> or
> a6a198bc60e6 ("xen/x86: Update topology map for PV VCPUs")
>
> and there are more.

I seriously hope there is a compatible way to get the hypervisor side
correct without breaking the Linux-side, otherwise we are going to have
some hard decisions to make about which scenarios we can afford to regress.

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

      reply	other threads:[~2017-03-02 20:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-02 14:42 Xen-unstable: Bisected Host boot failure on AMD Phenom Sander Eikelenboom
2017-03-02 14:55 ` Andrew Cooper
2017-03-02 17:29   ` Sander Eikelenboom
2017-03-02 17:38     ` Andrew Cooper
2017-03-02 18:25       ` Sander Eikelenboom
2017-03-02 18:29         ` Andrew Cooper
2017-03-02 18:51           ` Sander Eikelenboom
2017-03-02 18:56             ` Andrew Cooper
2017-03-02 19:15               ` Boris Ostrovsky
2017-03-02 19:17                 ` Andrew Cooper
2017-03-02 19:28                   ` Sander Eikelenboom
2017-03-02 19:36                     ` Andrew Cooper
2017-03-02 19:33                   ` Boris Ostrovsky
2017-03-02 20:02                     ` Andrew Cooper [this message]

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=fd340e81-8aca-e933-8591-2690a20ba360@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=jbeulich@suse.com \
    --cc=linux@eikelenboom.it \
    --cc=xen-devel@lists.xen.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.