xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Paul Durrant <Paul.Durrant@citrix.com>
To: Yu Zhang <yu.c.zhang@linux.intel.com>, Jan Beulich <JBeulich@suse.com>
Cc: Kevin Tian <kevin.tian@intel.com>,
	Andrew Cooper <Andrew.Cooper3@citrix.com>,
	"Tim (Xen.org)" <tim@xen.org>,
	George Dunlap <George.Dunlap@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	"zhiyuan.lv@intel.com" <zhiyuan.lv@intel.com>,
	Jun Nakajima <jun.nakajima@intel.com>
Subject: Re: [PATCH v5 3/4] x86/ioreq server: Add HVMOP to map guest ram with p2m_ioreq_server to an ioreq server.
Date: Tue, 9 Aug 2016 09:07:01 +0000	[thread overview]
Message-ID: <fe2c3382e1de4be7aa4d397bc9cc26e7@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <57A9997A.1080300@linux.intel.com>

> -----Original Message-----
> From: Yu Zhang [mailto:yu.c.zhang@linux.intel.com]
> Sent: 09 August 2016 09:51
> To: Paul Durrant; Jan Beulich
> Cc: Andrew Cooper; George Dunlap; Jun Nakajima; Kevin Tian;
> zhiyuan.lv@intel.com; xen-devel@lists.xen.org; Tim (Xen.org)
> Subject: Re: [Xen-devel] [PATCH v5 3/4] x86/ioreq server: Add HVMOP to
> map guest ram with p2m_ioreq_server to an ioreq server.
> 
> 
> 
> On 8/9/2016 4:20 PM, Paul Durrant wrote:
> >> -----Original Message-----
> >> From: Jan Beulich [mailto:JBeulich@suse.com]
> >> Sent: 09 August 2016 09:11
> >> To: Paul Durrant; Yu Zhang
> >> Cc: Andrew Cooper; George Dunlap; Jun Nakajima; Kevin Tian;
> >> zhiyuan.lv@intel.com; xen-devel@lists.xen.org; Tim (Xen.org)
> >> Subject: Re: [Xen-devel] [PATCH v5 3/4] x86/ioreq server: Add HVMOP to
> >> map guest ram with p2m_ioreq_server to an ioreq server.
> >>
> >>>>> On 09.08.16 at 09:39, <yu.c.zhang@linux.intel.com> wrote:
> >>> On 8/8/2016 11:40 PM, Jan Beulich wrote:
> >>>>>>> On 12.07.16 at 11:02, <yu.c.zhang@linux.intel.com> wrote:
> >>>>> +    rc = -ENOENT;
> >>>>> +    list_for_each_entry ( s,
> >>>>> +                          &d->arch.hvm_domain.ioreq_server.list,
> >>>>> +                          list_entry )
> >>>>> +    {
> >>>>> +        if ( s == d->arch.hvm_domain.default_ioreq_server )
> >>>>> +            continue;
> >>>>> +
> >>>>> +        if ( s->id == id )
> >>>>> +        {
> >>>>> +            rc = p2m_set_ioreq_server(d, flags, s);
> >>>>> +            if ( rc == 0 )
> >>>>> +                dprintk(XENLOG_DEBUG, "%u %s type
> >> HVMMEM_ioreq_server.\n",
> >>>>> +                         s->id, (flags != 0) ? "mapped to" : "unmapped from");
> >>>> Is this really useful?
> >>> Sorry, are you referring to this debug message?
> >>> I believe it helps, especially when multiple ioreq servers are
> >>> claiming/disclaiming their ownership of
> >>> the HVMMEM_ioreq_server. :)
> >> Well, that's a configuration bug anyway right now, so I'm not really
> >> with you. But in the end it'll be Paul to judge ...
> >>
> > Indeed, I don't the message has a massive amount of value. More useful
> would be to add a call into keyhandler.c:dump_domains() to display the
> current claim.
> >
> 
> All right. Let's remove this debug message. The debug key handler can be
> updated in a separate patch, is this OK? :-)
>

OK with me.

  Paul
 
> Yu

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2016-08-09  9:07 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-12  9:02 [PATCH v5 0/4] x86/ioreq server: Introduce HVMMEM_ioreq_server mem type Yu Zhang
2016-07-12  9:02 ` [PATCH v5 1/4] x86/ioreq server: Rename p2m_mmio_write_dm to p2m_ioreq_server Yu Zhang
2016-07-12  9:02 ` [PATCH v5 2/4] x86/ioreq server: Add new functions to get/set memory types Yu Zhang
2016-07-12  9:02 ` [PATCH v5 3/4] x86/ioreq server: Add HVMOP to map guest ram with p2m_ioreq_server to an ioreq server Yu Zhang
2016-08-08 15:40   ` Jan Beulich
2016-08-09  7:39     ` Yu Zhang
2016-08-09  8:11       ` Jan Beulich
2016-08-09  8:20         ` Paul Durrant
2016-08-09  8:51           ` Yu Zhang
2016-08-09  9:07             ` Paul Durrant [this message]
2016-08-10  8:09     ` Yu Zhang
2016-08-10 10:33       ` Jan Beulich
2016-08-10 10:43         ` Paul Durrant
2016-08-10 12:32           ` Yu Zhang
2016-08-10 10:43         ` Yu Zhang
2016-08-11  8:47           ` Yu Zhang
2016-08-11  8:58             ` Jan Beulich
2016-08-11  9:19               ` Yu Zhang
2016-07-12  9:02 ` [PATCH v5 4/4] x86/ioreq server: Reset outstanding p2m_ioreq_server entries when an ioreq server unmaps Yu Zhang
2016-08-08 16:29   ` Jan Beulich
2016-08-09  7:39     ` Yu Zhang
2016-08-09  8:13       ` Jan Beulich
2016-08-09  9:25         ` Yu Zhang
2016-08-09  9:45           ` Jan Beulich
2016-08-09 10:21             ` Yu Zhang
2016-08-16 13:35   ` George Dunlap
2016-08-16 13:54     ` Jan Beulich
2016-08-30 12:17     ` Yu Zhang
2016-09-02 11:00       ` Yu Zhang
2016-08-05  2:44 ` [PATCH v5 0/4] x86/ioreq server: Introduce HVMMEM_ioreq_server mem type Yu Zhang
2016-08-05  6:16   ` Jan Beulich
2016-08-05 12:46   ` George Dunlap

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=fe2c3382e1de4be7aa4d397bc9cc26e7@AMSPEX02CL03.citrite.net \
    --to=paul.durrant@citrix.com \
    --cc=Andrew.Cooper3@citrix.com \
    --cc=George.Dunlap@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=jun.nakajima@intel.com \
    --cc=kevin.tian@intel.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xen.org \
    --cc=yu.c.zhang@linux.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 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).