All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>,
	daniel.kiper@oracle.com, eshelton@pobox.com
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	Mark Hurenkamp <mark.hurenkamp@xs4all.nl>
Subject: Re: Xen 4.4 trunk: device [xxxx:yyyy] has invalid IRQ; check vendor BIOS
Date: Wed, 27 Nov 2013 09:43:22 -0500	[thread overview]
Message-ID: <20131127144321.GH4430@pegasus.dumpdata.com> (raw)
In-Reply-To: <529606F90200007800107964@nat28.tlf.novell.com>

On Wed, Nov 27, 2013 at 01:51:37PM +0000, Jan Beulich wrote:
> >>> On 26.11.13 at 22:38, Mark Hurenkamp <mark.hurenkamp@xs4all.nl> wrote:
> > Thanks for your response, i wasn't sure if this was the right place to 
> > address this, so i kept my initial mail short. However I would indeed 
> > appreciate any help that can point me into the direction of a more 
> > useable xen installation on this system.
> > So brace yourself for some information ;-)
> > 
> > xen.cfg:
> > ========
> 
> So you're booting from EFI, with a kernel not capable of this. Hence
> ACPI isn't being used, and consequently it's surprising that at least
> some of your interrupts appear to work.
> 
> You could have found this by searching e.g. the mailing list archives;
> you're not the first one to encounter this.

CC-ing Daniel and Eric

Eric Shelton posted some patches:
 http://lists.xen.org/archives/html/xen-devel/2013-08/msg01505.html

that would allow your Linux kernel to take advantage of it.
But they are not yet upstream-quality. I had provided some
ideas of how to make this fit within the model - but I fear
Eric got buried with other TODOs.

> 
> Jan
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  reply	other threads:[~2013-11-27 14:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-25 19:16 Xen 4.4 trunk: device [xxxx:yyyy] has invalid IRQ; check vendor BIOS Mark Hurenkamp
2013-11-25 21:43 ` Mark Hurenkamp
2013-11-26  8:40   ` Jan Beulich
2013-11-26 21:38     ` Mark Hurenkamp
2013-11-26 21:46       ` Andrew Cooper
2013-11-26 23:50         ` Mark Hurenkamp
2013-11-27  9:30       ` Jan Beulich
2013-11-27 13:51       ` Jan Beulich
2013-11-27 14:43         ` Konrad Rzeszutek Wilk [this message]
2013-11-27 21:45           ` Mark Hurenkamp
2013-11-27 16:20         ` Mark Hurenkamp

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=20131127144321.GH4430@pegasus.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=daniel.kiper@oracle.com \
    --cc=eshelton@pobox.com \
    --cc=mark.hurenkamp@xs4all.nl \
    --cc=xen-devel@lists.xenproject.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.