From: Jan Kiszka <jan.kiszka@web.de>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
"Alexander Graf" <agraf@suse.de>,
"Andreas Färber" <andreas.faerber@web.de>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Aurelien Jarno" <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [STABLE][PATCH] isa-bus: Remove bogus IRQ sharing check
Date: Sun, 20 Feb 2011 10:01:32 +0100 [thread overview]
Message-ID: <4D60D86C.6090604@web.de> (raw)
In-Reply-To: <4D6047EE.50707@msgid.tls.msk.ru>
[-- Attachment #1: Type: text/plain, Size: 2289 bytes --]
On 2011-02-19 23:45, Michael Tokarev wrote:
> 19.02.2011 20:56, Jan Kiszka wrote:
>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>
>> Nothing prevented IRQ sharing on the ISA bus in principle. Not all
>> boards supported this, neither each and every card nor driver and OS.
>> Still, there existed valid IRQ sharing scenarios, (at least) two of them
>> can also be found in QEMU: >2 PC UARTs and the PREP IDE buses.
>>
>> So remove this artificial restriction from our ISA model and reenable
>> both PREP IDE buses.
>
> In qemu-kvm at least (I don't remember how different the relevant code
> has been between qemu and qemu-kvm at that time) this restriction exists
Both trees should not have had any differences in this area.
> since 0.12 version. Before that it was at least possible to have >2 UARTS.
> Do you aware of this? I don't know this code at all, so.. just asking :)
Oh, we have this since 0.13? Well...
>
> I'd love to get this fixed for real instead of a hackish way we did this
> in the debian package, and it does not look like the change is problematic,
> but are you sure it should go to stable?
If we agree that removing is correct (I'm strongly convinced about
this), than at least 0.14.1 should benefit from it.
>
> FWIW, I applied this patch to qemu-kvm 0.14 branch (had to hand-apply
> it to hw/pc.c, obvious s/isa_reserve_irq/isa_get_irq) and run some quick
> tests, it appears to work correctly here with multiple serial ports
> and e.g. serial console on ttyS4.
>
> (Without the patch (and this is a separate bug), qemu-kvm prints:
>
> qemu: hardware error: isa irq 4 already assigned
> CPU #0:
> _
>
> when asked to create 3 serial ports, and stays there till killed).
Yeah, saw this at well but somehow ignored it. It's a KVM bug, upstream
is fixed like this:
diff --git a/kvm-all.c b/kvm-all.c
index e6a7de4..e54b5bf 100644
--- a/kvm-all.c
+++ b/kvm-all.c
@@ -211,6 +211,7 @@ int kvm_init_vcpu(CPUState *env)
env->kvm_fd = ret;
env->kvm_state = s;
+ env->kvm_vcpu_dirty = 1;
mmap_size = kvm_ioctl(s, KVM_GET_VCPU_MMAP_SIZE, 0);
if (mmap_size < 0) {
Will queue this for uq/master and post a corresponding qemu-kvm patch.
Thanks for pointing out!
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
next prev parent reply other threads:[~2011-02-20 9:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-19 17:56 [Qemu-devel] [STABLE][PATCH] isa-bus: Remove bogus IRQ sharing check Jan Kiszka
2011-02-19 22:45 ` Michael Tokarev
2011-02-20 9:01 ` Jan Kiszka [this message]
2011-02-19 23:25 ` [Qemu-devel] " Aurelien Jarno
2011-02-20 9:00 ` Jan Kiszka
2011-02-21 16:43 ` [Qemu-devel] " Aurelien Jarno
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=4D60D86C.6090604@web.de \
--to=jan.kiszka@web.de \
--cc=agraf@suse.de \
--cc=andreas.faerber@web.de \
--cc=aurelien@aurel32.net \
--cc=kraxel@redhat.com \
--cc=kwolf@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@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).