All of lore.kernel.org
 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 12:14:45 +0200	[thread overview]
Message-ID: <52134195.6040900@redhat.com> (raw)
In-Reply-To: <1376990796.25016.140.camel@pasglop>

Il 20/08/2013 11:26, Benjamin Herrenschmidt ha scritto:
> On Tue, 2013-08-20 at 11:22 +0200, Paolo Bonzini wrote:
>>
>> Uhm... I thought Alex and I were the one who proposed the simple things.
>>  You _will_ need to do the complicated stuff sooner or later, but it's
>> probably early enough now to ignore it.
>>
>> And I'm not saying this out of love for big cathedrals, but out of
>> lessons we learned the hard way for x86 (where we haven't gotten
>> everything right yet, either).
> 
> I suppose if RH is going to deploy 3.10 and we aren't going to backport
> the multitce patches then there *might* be a case for supporting that
> combo specifically... but it's going to be that bad every time we add
> a new feature with a kernel counter part or start adding the gazillion
> little bits of PAPR that we are still missing ?

Yes. :(

Unless you consider pSeries KVM not mature enough to provide a guest ABI
(basically supporting live migration only between identical kernels and
QEMUs).  It would make some sense, for example (mutatis mutandis) Red
Hat has a kernel ABI for the "regular" RHEL kernel, but not for the
"real-time" RHEL kernel.

Paolo

  reply	other threads:[~2013-08-20 10:15 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
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 [this message]
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=52134195.6040900@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 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.