qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 8/9] isa: refine irq reservations
Date: Tue, 15 Sep 2009 22:08:16 +0300	[thread overview]
Message-ID: <f43fc5580909151208q4c920a9bi861e5cfa39d453e4@mail.gmail.com> (raw)
In-Reply-To: <4AAF40FD.5020205@redhat.com>

On Tue, Sep 15, 2009 at 10:23 AM, Gerd Hoffmann <kraxel@redhat.com> wrote:
> On 09/14/09 18:55, Blue Swirl wrote:
>>
>> On Mon, Sep 14, 2009 at 6:49 PM, Gerd Hoffmann<kraxel@redhat.com>  wrote:
>>>
>>> There are a few cases where IRQ sharing on the ISA bus is used and
>>> possible.  In general only devices of the same kind can do that.
>>> A few use cases:
>>>
>>>  * serial lines 1+3 share irq 4
>>>  * serial lines 2+4 share irq 3
>>>  * parallel ports share irq 7
>>>  * ppc/prep: ide ports share irq 13
>>
>> There is another ppc/prep case where RTC and m48t59 share irq 8. The
>> attached patch converts m48t59 to ISA and makes this more visible.
>
> Hmm, ok.  So scratch this and maybe use a 'sharing the irq is is fine with
> me' flag instead?
>
>> Does sharing of IRQs really have to be fatal? Wasn't ISA bus edge
>> triggered and so IRQ sharing was a bit unreliable (but not completely
>> broken) also on real HW?
>
> Well, the fundamental problem is that (1) the drivers must be prepared to
> handle that and (b) the hardware must be designed sanely.  There are cases
> where it works fine (see the list above).  It isn't true in general though.
>  You can't configure two random devices (say sb16 + ne2k) to share the same
> irq and expect everything to work fine.

I wonder if the PREP machine is emulated correctly. I couldn't find
docs about PREP NVRAM or RTC.

  reply	other threads:[~2009-09-15 19:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-14 15:49 [Qemu-devel] [PATCH 0/9] ide: convert to qdev Gerd Hoffmann
2009-09-14 15:49 ` [Qemu-devel] [PATCH 1/9] qdev/pci: add pci_create_noinit() Gerd Hoffmann
2009-09-14 15:49 ` [Qemu-devel] [PATCH 2/9] support media=cdrom for if=none Gerd Hoffmann
2009-09-14 15:49 ` [Qemu-devel] [PATCH 3/9] split away drive init from ide_init2() Gerd Hoffmann
2009-09-14 15:49 ` [Qemu-devel] [PATCH 4/9] ide/qdev: add ide bus Gerd Hoffmann
2009-09-14 15:49 ` [Qemu-devel] [PATCH 5/9] ide/pci: fix indention Gerd Hoffmann
2009-09-14 15:49 ` [Qemu-devel] [PATCH 6/9] ide/pci: convert to qdev Gerd Hoffmann
2009-09-14 15:49 ` [Qemu-devel] [PATCH 7/9] ide/isa: " Gerd Hoffmann
2009-09-14 17:23   ` Blue Swirl
2009-09-14 17:46     ` Blue Swirl
2009-09-15  9:33       ` Gerd Hoffmann
2009-09-15 20:10         ` Blue Swirl
2009-09-14 15:49 ` [Qemu-devel] [PATCH 8/9] isa: refine irq reservations Gerd Hoffmann
2009-09-14 16:55   ` Blue Swirl
2009-09-14 20:09     ` Markus Armbruster
2009-09-15  7:23     ` Gerd Hoffmann
2009-09-15 19:08       ` Blue Swirl [this message]
2009-09-14 15:49 ` [Qemu-devel] [PATCH 9/9] unbreak ppc/prep Gerd Hoffmann
2009-09-23 19:00 ` [Qemu-devel] [PATCH 0/9] ide: convert to qdev Markus Armbruster

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=f43fc5580909151208q4c920a9bi861e5cfa39d453e4@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=kraxel@redhat.com \
    --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).