From: Keir Fraser <keir@xensource.com>
To: Lukas Hejtmanek <xhejtman@ics.muni.cz>, xen-devel@lists.xensource.com
Subject: Re: Permissive devices in Xen
Date: Sun, 08 Jul 2007 10:55:16 +0100 [thread overview]
Message-ID: <C2B67314.A7E1%keir@xensource.com> (raw)
In-Reply-To: <20070708010556.GW3885@ics.muni.cz>
On 8/7/07 02:05, "Lukas Hejtmanek" <xhejtman@ics.muni.cz> wrote:
> The PCI_COMMAND is handled in special way so that the device is
> enabled/disabled properly, am I right?
>
> Why is PCI_INTERRUPT_LINE read from dev->irq and not from the config space?
dom0 will have correctly routed the interrupt,a nd stored the correct irq
number in dev->irq. The number in the config space may not be correct, or
may indicate only the irq number for legacy PCI-ISA link.
> Why the PCI address bars are handled in very different way? And it seems that
> writing these bars is never committed to the real devices. Why?
domU is not trusted to manage the i/o address space. We assume dom0 has set
up the values sanely and domU should have no reason to change them.
-- Keir
next prev parent reply other threads:[~2007-07-08 9:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-08 1:05 Permissive devices in Xen Lukas Hejtmanek
2007-07-08 9:55 ` Keir Fraser [this message]
2007-07-08 10:00 ` Lukas Hejtmanek
2007-07-08 10:10 ` Keir Fraser
2007-07-09 23:14 ` Lukas Hejtmanek
2007-07-10 8:31 ` Keir Fraser
2007-07-10 8:57 ` Lukas Hejtmanek
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=C2B67314.A7E1%keir@xensource.com \
--to=keir@xensource.com \
--cc=xen-devel@lists.xensource.com \
--cc=xhejtman@ics.muni.cz \
/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.