From: "Yu, Zhang" <yu.c.zhang@linux.intel.com>
To: Tim Deegan <tim@xen.org>
Cc: kevin.tian@intel.com, keir@xen.org, ian.campbell@citrix.com,
stefano.stabellini@eu.citrix.com, ian.jackson@eu.citrix.com,
donald.d.dugger@intel.com, Xen-devel@lists.xen.org,
Paul.Durrant@citrix.com, zhiyuan.lv@intel.com,
Jan Beulich <JBeulich@suse.com>,
yang.z.zhang@intel.com
Subject: Re: [PATCH v4] x86: add p2m_mmio_write_dm
Date: Thu, 04 Dec 2014 17:42:40 +0800 [thread overview]
Message-ID: <54802C90.1030401@linux.intel.com> (raw)
In-Reply-To: <20141204093600.GA35555@deinos.phlegethon.org>
On 12/4/2014 5:36 PM, Tim Deegan wrote:
> Hi,
>
> At 17:01 +0800 on 04 Dec (1417708878), Yu, Zhang wrote:
>> I just noticed that in __hvm_copy()/__hvm_clear(), the grant types are
>> handled before the p2m_ram_ro - will return HVMCOPY_unhandleable. So if
>> p2m_is_discard_write() is supposed to replace the handling of
>> p2m_ram_ro, handling of p2m_grant_map_ro will still return
>> HVMCOPY_unhandleable, before the p2m_is_discard_write() predicate.
>> Even we move the testing of p2m_is_discard_write() before the handling
>> of grant types, it seems not quite clean.
>> By "over-strict in their failure to handle grant types.", do you also
>> mean this?
>
> Yes, that's the sort of thing I meant. I'll try to write a patch for
> that later today or next week -- in the meantime I think you should
> ignore it. :)
>
> An unrelated thought: when you send your next version can you send it
> as a two-patch series, where the first patch does the
> p2m_is_discard_write() changes and the second adds your new type?
Sure, and thank you, Tim. :)
>
> Cheers,
>
> Tim.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
>
prev parent reply other threads:[~2014-12-04 9:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 7:59 [PATCH v4] x86: add p2m_mmio_write_dm Yu Zhang
2014-11-28 9:57 ` Jan Beulich
2014-12-01 8:49 ` Yu, Zhang
2014-12-01 9:32 ` Jan Beulich
2014-12-01 10:30 ` Tim Deegan
2014-12-01 11:17 ` Jan Beulich
2014-12-01 12:13 ` Tim Deegan
2014-12-01 12:31 ` Jan Beulich
2014-12-02 7:48 ` Yu, Zhang
2014-12-02 9:39 ` Jan Beulich
2014-12-02 10:37 ` Tim Deegan
2014-12-02 11:03 ` Jan Beulich
2014-12-02 7:38 ` Yu, Zhang
2014-12-02 11:40 ` Tim Deegan
2014-12-02 11:52 ` Jan Beulich
2014-12-03 6:58 ` Yu, Zhang
2014-12-04 9:01 ` Yu, Zhang
2014-12-04 9:36 ` Tim Deegan
2014-12-04 9:42 ` Yu, Zhang [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=54802C90.1030401@linux.intel.com \
--to=yu.c.zhang@linux.intel.com \
--cc=JBeulich@suse.com \
--cc=Paul.Durrant@citrix.com \
--cc=Xen-devel@lists.xen.org \
--cc=donald.d.dugger@intel.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=keir@xen.org \
--cc=kevin.tian@intel.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--cc=yang.z.zhang@intel.com \
--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 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.