All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Philip Wernersbach <philip.wernersbach@gmail.com>,
	daniel.kiper@oracle.com
Cc: Jan Beulich <JBeulich@suse.com>, xen-devel@lists.xen.org
Subject: Re: [PATCH][v2] xen: Pass the location of the ACPI RSDP to DOM0.
Date: Tue, 21 Jan 2014 16:31:17 -0500	[thread overview]
Message-ID: <20140121213117.GA6003@phenom.dumpdata.com> (raw)
In-Reply-To: <CAO5Rg120ihzBdgsvDSf2BC4BAYtFznfyCcORtTBjhXs7wquiHA@mail.gmail.com>

On Tue, Jan 21, 2014 at 04:19:40PM -0500, Philip Wernersbach wrote:
> On Tue, Jan 21, 2014 at 4:51 AM, Jan Beulich <JBeulich@suse.com> wrote:
> >>>> On 20.01.14 at 23:08, Philip Wernersbach <philip.wernersbach@gmail.com> wrote:
> >> xen: [v2] Pass the location of the ACPI RSDP to DOM0.
> >>
> >> Some machines, such as recent IBM servers, only allow the OS to get the
> >> ACPI RSDP from EFI. Since Xen nukes DOM0's ability to access EFI, DOM0
> >
> > This reads as if this was a bug in Xen, which it isn't. Dom0's
> > lack of EFI support when running on top of Xen is the issue.
> 
> It all depends on how you look at it, as there's two ways to fix this.
> Linux currently supports EFI just fine. Xen nukes DOM0's ability to
> access EFI using the current methods, which causes Linux's existing
> EFI support to fail. This would be Xen's fault. If Xen currently
> exposes EFI to DOM0 in some other way that Linux is not aware of, then
> this would be Linux's fault. Either way, we can either choose to fix
> Xen or fix Linux.
> 
> > I think I had indicated my opposition to this sort of hack on v1
> > already; I'm not sure I asked which OSes usable as Dom0 but
> > other than Linux recognize this option. Or which versions of
> > Linux actually do (I'm pretty sure older ones don't).
> >
> > Bottom line - I continue to think that the issue should be fixed
> > in Linux.
> 
> The method that this patch uses is a valid way to fix this. In the
> best case, the DOM0 OS recognizes this option and uses it. In the
> worst case, the DOM0 OS won't recognize the option and will ignore it,
> so we're no worse off.
> 
> I agree with you that this is more of a stop gap than a long term fix.
> The final solution is to fully expose EFI services to the DOM0 in some
> way. However, getting there will take some time. The reason this patch
> came about is that the company I work for bought new IBM servers in
> the hope of migrating our existing Xen server farm to the new IBM
> servers. But we soon found out that DOM0 couldn't find the ACPI RSDP
> pointer on the new IBM servers, which means that Xen is dead in the
> water on these machines for now. The final solution of exposing EFI to
> the DOM0 is the ultimate goal, but for now businesses need an
> immediate solution. This provides an acceptable solution until DOM0
> EFI services are implemented at a later date. There is no reason why
> this can't be merged now and then removed when DOM0 EFI service
> support arrives.

Could you use the Linux patches that use Xen's EFI services? Ie,
the DOM0 EFI ones?

They were posted on the mailing list some time ago (last year, November-ish?)
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  reply	other threads:[~2014-01-21 21:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-20 22:08 [PATCH][v2] xen: Pass the location of the ACPI RSDP to DOM0 Philip Wernersbach
2014-01-21  1:11 ` Andrew Cooper
2014-01-21  9:51 ` Jan Beulich
2014-01-21 21:19   ` Philip Wernersbach
2014-01-21 21:31     ` Konrad Rzeszutek Wilk [this message]
2014-01-21 22:09       ` Philip Wernersbach
2014-01-22  4:35         ` Konrad Rzeszutek Wilk
2014-01-22  8:42     ` Jan Beulich

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=20140121213117.GA6003@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=daniel.kiper@oracle.com \
    --cc=philip.wernersbach@gmail.com \
    --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.