From: Paolo Bonzini <pbonzini@redhat.com>
To: Thomas Huth <thuth@redhat.com>,
David Gibson <david@gibson.dropbear.id.au>
Cc: lvivier@redhat.com, qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] spapr: Reduce advertised max LUNs for spapr_vscsi
Date: Wed, 9 Sep 2015 14:09:45 +0200 [thread overview]
Message-ID: <55F02189.2080003@redhat.com> (raw)
In-Reply-To: <55EFDFCE.2040609@redhat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 09/09/2015 09:29, Thomas Huth wrote:
>> Doesn't help for existing guests. Basically what I'm trying to
>> achieve is for qemu to reject up-front configurations that are
>> unlikely to actually work in the guest.
>
> I just wonder whether it makes sense to change the guest instead.
I agree; perhaps it's a one-liner.
The patch is simple, but I wonder if it is really a case of "if it
hurts, don't do it".
Paolo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJV8CGFAAoJEL/70l94x66DhAYH/jlUe5xCT6YS5uiYQukrPrVC
rjJAzqLUUdKh62GHR62wKkylVds9YtFYlkLGLbaXUDO0uVlgvyr4BrPZ8xeKcfPg
3yMtoFIZr3rLdsY1Bbjk/ReyY5uU9fRvU8WHCSXeCsWqMUmFpMm7HdnbCdh+3mCW
bNUUuBorxCQMI+2ra8FNLCc/wMmw4M4M0uUtcGYOwxUkfcjPbQyqWFOtbj3Q2Mo9
CrGjW8u48ZFgiPMtHPI+hetZQBrMltoqokCl0Ca2DuWRK8pmSERDS7NqlNfzWDiL
/dyKkznPuWB4jox/NyeMpXmPMSgrwcSg3YvBv8My3EOiIcPp8b+nGCTLCkmbjzw=
=3vF9
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-09-09 12:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 1:22 [Qemu-devel] [PATCH] spapr: Reduce advertised max LUNs for spapr_vscsi David Gibson
2015-09-09 3:39 ` [Qemu-devel] [PATCHEW] Series failed testing Patchew Jenkins
2015-09-09 3:57 ` Fam Zheng
2015-09-09 6:25 ` [Qemu-devel] [PATCH] spapr: Reduce advertised max LUNs for spapr_vscsi Thomas Huth
2015-09-09 7:19 ` David Gibson
2015-09-09 7:29 ` Thomas Huth
2015-09-09 12:09 ` Paolo Bonzini [this message]
2015-09-10 1:24 ` David Gibson
2015-09-10 6:12 ` Thomas Huth
2015-09-10 6:48 ` David Gibson
2015-09-10 10:31 ` Laurent Vivier
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=55F02189.2080003@redhat.com \
--to=pbonzini@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=lvivier@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@redhat.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 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.