From: Luiz Capitulino <lcapitulino@redhat.com>
To: Anthony Liguori <aliguori@linux.vnet.ibm.com>
Cc: Huang Ying <ying.huang@intel.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
Avi Kivity <avi@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Andi Kleen <andi@firstfloor.org>,
Dean Nelson <dnelson@redhat.com>
Subject: Re: [PATCH -v2] Monitor command: pfa2hva, translate guest physical address to host virtual address
Date: Thu, 4 Nov 2010 14:53:42 -0200 [thread overview]
Message-ID: <20101104145342.4627dd9d@doriath> (raw)
In-Reply-To: <4CCF136D.5080307@linux.vnet.ibm.com>
On Mon, 01 Nov 2010 14:22:21 -0500
Anthony Liguori <aliguori@linux.vnet.ibm.com> wrote:
> On 11/01/2010 02:20 PM, Huang Ying wrote:
> > Yes. As general interface, it may not work so well, but as test
> > interface, it works quite well and useful.
> >
> > Do we have any mechanism to add a test only interface?
No.
We're likely going to introduce a new namespace for that in the near future,
but only for QMP.
Is this command supposed to be useful for applications or is it primary
designed for (human) debugging?
> I'd like to see what Luiz/Markus think but definitely only a human
> monitor interface and probably prefix the command with a 'x-' prefix to
> indicate that it's not a supported interface.
Yes, I agree on having only the human interface but I'm not sure about
prexing it with 'x-'. I think new HMP commands should be declared unstable
by default starting with 0.14.
> The documentation should be very clear about the limitations of the
> interface and the intended use-case.
>
> Regards,
>
> Anthony Liguori
>
> > Best Regards,
> > Huang Ying
> >
> >
> >
>
next prev parent reply other threads:[~2010-11-04 16:53 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 2:39 [PATCH -v2] Monitor command: pfa2hva, translate guest physical address to host virtual address Huang Ying
2010-11-01 16:09 ` Marcelo Tosatti
2010-11-01 18:49 ` Anthony Liguori
2010-11-01 19:20 ` Huang Ying
2010-11-01 19:22 ` Anthony Liguori
2010-11-04 16:53 ` Luiz Capitulino [this message]
2010-11-06 16:24 ` Avi Kivity
2010-11-08 1:29 ` Huang Ying
2010-11-08 3:39 ` Anthony Liguori
2010-11-08 20:46 ` Huang Ying
2010-11-09 3:06 ` Huang Ying
2010-11-10 6:56 ` Avi Kivity
2010-11-10 6:59 ` Avi Kivity
2010-11-10 7:41 ` Huang Ying
2010-11-10 8:28 ` Avi Kivity
2010-11-10 8:38 ` Huang Ying
2010-11-10 8:48 ` Avi Kivity
2010-11-10 16:42 ` Andi Kleen
2010-11-10 17:08 ` Avi Kivity
2010-11-10 17:44 ` Andi Kleen
2010-11-10 17:47 ` Avi Kivity
2010-11-10 19:16 ` Andi Kleen
2010-11-10 20:58 ` Avi Kivity
2010-11-10 8:21 ` Huang Ying
2010-11-10 8:34 ` Avi Kivity
2010-11-10 16:49 ` Anthony Liguori
2010-11-11 0:56 ` Huang Ying
2010-11-11 9:39 ` Avi Kivity
2010-11-12 1:16 ` Huang Ying
2010-11-14 11:08 ` Avi Kivity
2010-11-14 11:09 ` Avi Kivity
2010-11-15 1:46 ` Huang Ying
2010-11-15 10:02 ` Andi Kleen
2010-11-08 3:37 ` Anthony Liguori
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=20101104145342.4627dd9d@doriath \
--to=lcapitulino@redhat.com \
--cc=aliguori@linux.vnet.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=andi@firstfloor.org \
--cc=avi@redhat.com \
--cc=dnelson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=ying.huang@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