From: Wei Liu <wei.liu2@citrix.com>
To: Quan Xu <quan.xu@intel.com>
Cc: yang.z.zhang@intel.com, kevin.tian@intel.com,
wei.liu2@citrix.com, jbeulich@suse.com, xen-devel@lists.xen.org
Subject: Re: [PATCH] vt-d: Fix IM bit unmask of Fault Event Control Register in init_vtd_hw().
Date: Fri, 25 Sep 2015 19:57:10 +0100 [thread overview]
Message-ID: <20150925185710.GA8754@zion.uk.xensource.com> (raw)
In-Reply-To: <1443165755-89680-1-git-send-email-quan.xu@intel.com>
On Fri, Sep 25, 2015 at 03:22:35PM +0800, Quan Xu wrote:
> Bit 0:29 in Fault Event Control Register are 'Reserved and Preserved',
> software cannot write 0 to it unconditionally. Software must preserve
> the value read for writes.
>
> Signed-off-by: Quan Xu <quan.xu@intel.com>
> Reported-by: Jan Beulich <jbeulich@suse.com>
Release-acked-by: Wei Liu <wei.liu2@citrix.com>
prev parent reply other threads:[~2015-09-25 18:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 7:22 [PATCH] vt-d: Fix IM bit unmask of Fault Event Control Register in init_vtd_hw() Quan Xu
2015-09-25 18:57 ` Wei Liu [this message]
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=20150925185710.GA8754@zion.uk.xensource.com \
--to=wei.liu2@citrix.com \
--cc=jbeulich@suse.com \
--cc=kevin.tian@intel.com \
--cc=quan.xu@intel.com \
--cc=xen-devel@lists.xen.org \
--cc=yang.z.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).