linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "tiejun.chen" <tiejun.chen@windriver.com>
To: Alexander Graf <agraf@suse.de>,
	Caraman Mihai Claudiu-B02008 <B02008@freescale.com>
Cc: Scott Wood <scottwood@freescale.com>,
	Wood Scott-B07421 <B07421@freescale.com>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"kvm-ppc@vger.kernel.org" <kvm-ppc@vger.kernel.org>
Subject: Re: [v1][KVM][PATCH 1/1] kvm:ppc:booehv: direct ISI exception to Guest
Date: Mon, 13 May 2013 10:04:32 +0800	[thread overview]
Message-ID: <51904A30.8010408@windriver.com> (raw)
In-Reply-To: <F3847E9E-D4F6-4727-B3A6-42C68797F5CF@suse.de>

On 05/11/2013 03:39 AM, Alexander Graf wrote:
>
>
> Am 10.05.2013 um 21:22 schrieb Scott Wood <scottwood@freescale.com>:
>
>> On 05/10/2013 12:57:33 PM, Alexander Graf wrote:
>>> Could you guys please collect performance data during the next weeks on both guest-directed ISIs as well as VF MMIOs (preferably with in-kernel MMIO), so that we can decide on the direction that's worth going towards?
>>
>> Collecting data on VF MMIO would require implementing it (or at least salvaging and fixing some old code), which is not a high priority at the moment.  If we do implement VF in the future we could always undo the direct ISI change, but it would still be nice to know if there's any real benefit in the first place.
>
> Mike sounded like he had an almost working poc, which is good enough to collect rough numbers.

Which can the test case be adopted?

Mike,

If you already have a good case for your poc, please share that with me. Then 
I'd like to run that.

Tiejun

>
> And yes, changes like these should always get at least basic performance numbers along with them, regardless of drawbacks.
>
>
> Alex
>
>>
>> FWIW, I doubt that the "more stress on HW TLB" will be significant.
>>
>> -Scott
>

  reply	other threads:[~2013-05-13  2:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-07 11:06 [v1][KVM][PATCH 1/1] kvm:ppc:booehv: direct ISI exception to Guest Tiejun Chen
2013-05-07 23:40 ` Scott Wood
2013-05-08  1:53   ` tiejun.chen
2013-05-08  9:20     ` Caraman Mihai Claudiu-B02008
2013-05-08  9:28       ` tiejun.chen
2013-05-09 10:23         ` tiejun.chen
2013-05-09 11:34           ` Caraman Mihai Claudiu-B02008
2013-05-09 11:40             ` tiejun.chen
2013-05-09 12:36               ` Caraman Mihai Claudiu-B02008
2013-05-10 17:57                 ` Alexander Graf
2013-05-10 19:22                   ` Scott Wood
2013-05-10 19:39                     ` Alexander Graf
2013-05-13  2:04                       ` tiejun.chen [this message]
2013-05-08 19:09     ` Scott Wood

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=51904A30.8010408@windriver.com \
    --to=tiejun.chen@windriver.com \
    --cc=B02008@freescale.com \
    --cc=B07421@freescale.com \
    --cc=agraf@suse.de \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=scottwood@freescale.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).