From: Hans Mueller <mcbeagle@gmx.de>
To: xen-devel@lists.xen.org
Subject: Re: XSA-36 / howto fix broken IVRS ACPI table
Date: Wed, 24 Apr 2013 22:03:54 +0200 [thread overview]
Message-ID: <2822407.UaCHNbxBlk@sheik-lin> (raw)
In-Reply-To: <51779C1D02000078000D0348@nat28.tlf.novell.com>
On Wednesday, 24. April 2013 07:47:25 Jan Beulich wrote:
> >>> On 23.04.13 at 19:11, Hans Mueller <mcbeagle@gmx.de> wrote:
> > However the problem seems not really to be fixed:
> > Interrupts generated within one domain can still harm other domains which
> > at least causes the kernel within these other domains to disable
> > interrupts.
> "The problem" being which problem? Even after looking back through
> the list archives, I haven't been able to spot a corresponding problem
> description. And if you resume a thread after several weeks without
> sufficiently quoting the original, it would be rather desirable for you
> to at least briefly summarize your original problem.
Perhaps it was unclear - better than 'the' problem might be 'a' problem - as
briefly described regarding interrupts becoming disabled across domain borders.
However, I don't want to address that problem in this thread in detail, I just
worry that the fixes applied to the BIOS are insufficient and want to check this
before starting a perhaps unnecessary discussion about the 'interrupt
problem'.
Since XSA-36 Xen disabled the I/O virtualisation because there was a
conflicting IOAPIC entry within the IVRS table (probably for the disabled
northbridge IOAPIC & using the handle/id for the enabled southbridge IOAPIC).
The manufacturer just removed this entry from the IVRS table which causes Xen
to no longer complain about conflicting IOAPIC entries and enabling per-device
vector maps.
So currently only the southbridge IOAPIC is enabled.
The question is whether the missing/disabled northbridge IOAPIC is a valid
setup or might/will it raise any problems.
> The same physical IRQ being shared by multiple devices is entirely
> independent of XSA-36, and if your Dom0/DomU kernels can't cope
> with that they are what need fixing.
Is it obvious that such problems are not caused by the missing northbridge
IOAPIC? I would then provide related details in a new thread.
Best Regards
Hans
next prev parent reply other threads:[~2013-04-24 20:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 19:04 XSA-36 / howto fix broken IVRS ACPI table Hans Mueller
2013-03-12 19:41 ` Boris Ostrovsky
2013-04-23 17:11 ` Hans Mueller
2013-04-24 6:47 ` Jan Beulich
2013-04-24 20:03 ` Hans Mueller [this message]
2013-04-25 9:36 ` Jan Beulich
-- strict thread matches above, loose matches on Subject: below --
2013-04-16 7:20 Eric Shelton
2013-04-23 23:39 Eric Shelton
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=2822407.UaCHNbxBlk@sheik-lin \
--to=mcbeagle@gmx.de \
--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.