From: Markus Armbruster <armbru@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Wainer dos Santos Moschetta <wainersm@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] apic: Make APIC ID limit error message clearer
Date: Wed, 05 Dec 2018 08:29:15 +0100 [thread overview]
Message-ID: <87in082zzo.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20181204182133.GD18284@habkost.net> (Eduardo Habkost's message of "Tue, 4 Dec 2018 16:21:33 -0200")
Eduardo Habkost <ehabkost@redhat.com> writes:
> On Mon, Dec 03, 2018 at 07:07:10PM -0200, Wainer dos Santos Moschetta wrote:
>>
>> On 11/26/2018 08:56 PM, Eduardo Habkost wrote:
>> > Remove the "apic initialization failed" prefix (it conveys no
>> > useful information), replace "invalid" with "too large", and add
>> > an error hint with two possible solutions for the problem.
>> >
>> > Before:
>> >
>> > $ qemu-system-x86_64 -machine q35 -smp 256
>> > qemu-system-x86_64: apic initialization failed. APIC ID 255 is invalid
>> >
>> > After:
>> >
>> > $ qemu-system-x86_64 -machine q35 -smp 256 -display none
>> > qemu-system-x86_64: APIC ID 255 is too large
>>
>> I would keep the problem "apic initialization failed" sentence. "APIC ID 255
>> is too large" is just the cause.
>
> I'm not sure I agree. "APIC initialization failed" doesn't
> convey any useful information to the user, does it?
Concur.
>> > Possible solutions:
>> > * Lowering the number of VCPUs on the -smp option
>> > * Using accel=kvm,kernel-irqchip=on or accel=kvm,kernel-irqchip=split
>> >
>> > Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
>> > ---
>> > I'm not sure this is the best way to provide usage hints to the
>> > user. Any suggestions?
>>
>> As a noob, I can testify that this kind of suggestion is very useful
>> although there seems to not have many on QEMU. On the other hand, I
>> understand it can make qemu verbose and so annoy people. Thus, maybe those
>> suggestions could be enabled/disabled via options (e.g. -show-hints)?
>
> I can't imagine who would be annoyed by them.
A few lines of hints are fine. Longer than that and the error becomes
hard to spot among the hints.
prev parent reply other threads:[~2018-12-05 7:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 22:56 [Qemu-devel] [PATCH] apic: Make APIC ID limit error message clearer Eduardo Habkost
2018-12-03 21:07 ` Wainer dos Santos Moschetta
2018-12-04 18:21 ` Eduardo Habkost
2018-12-05 7:29 ` Markus Armbruster [this message]
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=87in082zzo.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=ehabkost@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wainersm@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.