qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
	Alexander Graf <agraf@suse.de>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
	Paul Mackerras <paulus@samba.org>,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH] powerpc iommu: enable multiple TCE requests
Date: Tue, 20 Aug 2013 11:15:55 +0200	[thread overview]
Message-ID: <521333CB.1080407@redhat.com> (raw)
In-Reply-To: <1376989997.25016.131.camel@pasglop>

Il 20/08/2013 11:13, Benjamin Herrenschmidt ha scritto:
> On Tue, 2013-08-20 at 11:09 +0200, Paolo Bonzini wrote:
>>> Sorry if I miss anything, but is not it what the patch already
>> does? :)
>>
>> No, you need to expose multitce unconditionally in the device tree.
> 
> If I'm not mistaken the multitce kernel side patches are still not
> upstream so I disagree. Exposing it will make Linux use it which means
> that anything running on 3.10 or 3.11 will become very slow.
> 
> So no, multitce should not be exposed if KVM doesn't support it.

Then you have to do it right and:

- provide the infrastructure to enable/disable it from the command line
(which will be enough design effort alone);

- add pseries-1.6 as a synonym of pseries in 1.6.1;

- add pseries-1.7 a synonym of pseries in master;

- add a pseries-1.6 machine type in master that always disables it.

Paolo

  reply	other threads:[~2013-08-20  9:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-07  8:08 [Qemu-devel] [PATCH] powerpc iommu: enable multiple TCE requests Alexey Kardashevskiy
2013-08-16  9:49 ` Alexey Kardashevskiy
2013-08-18 15:22   ` Paolo Bonzini
2013-08-19  7:30     ` Alexey Kardashevskiy
2013-08-19  8:01       ` Alexander Graf
2013-08-19  8:44         ` Alexey Kardashevskiy
2013-08-19  9:47           ` Paolo Bonzini
2013-08-20  1:36             ` Alexey Kardashevskiy
2013-08-20  6:55               ` Alexander Graf
2013-08-20  8:39               ` Paolo Bonzini
2013-08-20  8:49                 ` Alexey Kardashevskiy
2013-08-20  9:09                   ` Paolo Bonzini
2013-08-20  9:13                     ` Benjamin Herrenschmidt
2013-08-20  9:15                       ` Paolo Bonzini [this message]
2013-08-20  9:20                         ` Benjamin Herrenschmidt
2013-08-20  9:22                           ` Paolo Bonzini
2013-08-20  9:26                             ` Benjamin Herrenschmidt
2013-08-20 10:14                               ` Paolo Bonzini
2013-08-20 11:38                                 ` Benjamin Herrenschmidt
2013-08-21  7:11                                   ` Alexander Graf
2013-08-21  7:29                                     ` [Qemu-devel] [Qemu-ppc] " Alexander Graf
2013-08-16 13:15 ` [Qemu-devel] " Alexander Graf
2013-08-19  9:01   ` Alexey Kardashevskiy

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=521333CB.1080407@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=agraf@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=benh@kernel.crashing.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=paulus@samba.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    /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).