From: "Jan Beulich" <JBeulich@novell.com>
To: xiantao.zhang@intel.com
Cc: xen-devel@lists.xensource.com
Subject: set_msi_affinity() vs. pci_restore_msi_state()
Date: Fri, 05 Mar 2010 16:03:52 +0000 [thread overview]
Message-ID: <4B9139780200007800033011@vpn.id2.novell.com> (raw)
Isn't the fact that the former updates the MSI message data without
updating the copy of it in memory a problem for the latter, i.e. won't
the latter restore stale information? While the problem (if there is one)
existed before c/s 20073, the fact that the vector now can change
seems to make the potential effect of this much worse.
Thanks, Jan
next reply other threads:[~2010-03-05 16:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-05 16:03 Jan Beulich [this message]
2010-03-08 2:14 ` set_msi_affinity() vs. pci_restore_msi_state() Zhang, Xiantao
2010-03-08 8:10 ` 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=4B9139780200007800033011@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=xen-devel@lists.xensource.com \
--cc=xiantao.zhang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).