From: Yu Zhang <yu.c.zhang@linux.intel.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Paul Durrant <paul.durrant@citrix.com>,
zhiyuan.lv@intel.com, xen-devel@lists.xen.org
Subject: Re: [PATCH v8 1/5] x86/ioreq server: Release the p2m lock after mmio is handled.
Date: Tue, 21 Mar 2017 09:18:38 +0800 [thread overview]
Message-ID: <58D07F6E.6060708@linux.intel.com> (raw)
In-Reply-To: <58D0196D02000078001454FD@prv-mh.provo.novell.com>
On 3/21/2017 1:03 AM, Jan Beulich wrote:
>>>> On 18.03.17 at 11:53, <yu.c.zhang@linux.intel.com> wrote:
>> --- a/xen/arch/x86/hvm/hvm.c
>> +++ b/xen/arch/x86/hvm/hvm.c
>> @@ -1870,18 +1870,14 @@ int hvm_hap_nested_page_fault(paddr_t gpa, unsigned long gla,
>> (npfec.write_access &&
>> (p2m_is_discard_write(p2mt) || (p2mt == p2m_ioreq_server))) )
>> {
>> - __put_gfn(p2m, gfn);
>> - if ( ap2m_active )
>> - __put_gfn(hostp2m, gfn);
>> -
>> rc = 0;
>> if ( unlikely(is_pvh_domain(currd)) )
>> - goto out;
>> + goto out_put_gfn;
> Did you forget to re-base onto staging before you've sent this?
> is_pvh_domain() was gone before your submission already. When
> re-basing, feel free to also drop the dead "rc = 0;" line.
Oops...
I did a rebase days ago, but did not send the patch directly. There were
some XenGT test performed based on these patch.
Sorry, I should have a check. Will resend the patch. :)
B.R.
Yu
> Jan
>
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-03-21 1:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-18 10:53 [PATCH v8 0/5] x86/ioreq server: Introduce HVMMEM_ioreq_server mem type Yu Zhang
2017-03-18 10:53 ` [PATCH v8 1/5] x86/ioreq server: Release the p2m lock after mmio is handled Yu Zhang
2017-03-20 17:03 ` Jan Beulich
2017-03-21 1:18 ` Yu Zhang [this message]
2017-03-21 2:43 ` Yu Zhang
2017-03-18 10:53 ` [PATCH v8 2/5] x86/ioreq server: Add DMOP to map guest ram with p2m_ioreq_server to an ioreq server Yu Zhang
2017-03-18 10:53 ` [PATCH v8 3/5] x86/ioreq server: Handle read-modify-write cases for p2m_ioreq_server pages Yu Zhang
2017-03-18 10:53 ` [PATCH v8 4/5] x86/ioreq server: Asynchronously reset outstanding p2m_ioreq_server entries Yu Zhang
2017-03-18 10:53 ` [PATCH v8 5/5] x86/ioreq server: Synchronously reset outstanding p2m_ioreq_server entries when an ioreq server unmaps Yu Zhang
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=58D07F6E.6060708@linux.intel.com \
--to=yu.c.zhang@linux.intel.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=paul.durrant@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=zhiyuan.lv@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).