All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Jan Beulich <jbeulich@novell.com>
Cc: Yunhong Jiang <yunhong.jiang@intel.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH][RFC] Support S3 for MSI interrupt in latest kernel dom0
Date: Wed, 17 Dec 2008 15:06:49 +0000	[thread overview]
Message-ID: <C56EC609.20544%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <49491F2B.76E4.0078.0@novell.com>

On 17/12/2008 14:47, "Jan Beulich" <jbeulich@novell.com> wrote:

>> Could Xen remember the MSI state automatically, as it does for IO-APIC
>> presumably already? It knows what vectors are routed where at least, even if
>> dom0 has to reprogram the PCI device itself.
> 
> That is what the map_guest_pirq() re-invocation is intended for - use the
> already known (stored) MSI state to re-setup the device accordingly
> (after all, msi_compose_msg() only depends on the vector information
> to be able to reconstruct address and data fields).

Why wait for map_guest_pirq() to be invoked to do this?

 -- Keir

  reply	other threads:[~2008-12-17 15:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-17 12:11 [PATCH][RFC] Support S3 for MSI interrupt in latest kernel dom0 Jiang, Yunhong
2008-12-17 12:27 ` Keir Fraser
2008-12-17 14:47   ` Jan Beulich
2008-12-17 15:06     ` Keir Fraser [this message]
2008-12-17 15:19       ` Jan Beulich
2008-12-17 15:22         ` Keir Fraser
2008-12-17 15:31           ` Jan Beulich
2008-12-17 15:53             ` Keir Fraser
2008-12-18  2:24               ` Jiang, Yunhong
2008-12-18  7:33                 ` Jan Beulich
2008-12-19 10:10                   ` Jiang, Yunhong
2008-12-19 10:29                     ` Jan Beulich
2008-12-19 10:39                       ` Jiang, Yunhong
2008-12-19 10:50                         ` 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=C56EC609.20544%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=jbeulich@novell.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=yunhong.jiang@intel.com \
    /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.