qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alessandro Corradi" <ale.corradi@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Interrupt request info
Date: Sun, 12 Nov 2006 16:46:00 +0100	[thread overview]
Message-ID: <b921df970611120746h79a94c4dnb5faa6b09fdbd12b@mail.gmail.com> (raw)
In-Reply-To: <200611012331.38312.paul@codesourcery.com>

[-- Attachment #1: Type: text/plain, Size: 1032 bytes --]

I tried with both pic_set_irq and pic_set_irq_new but nothing happen (the
irq number is 13 and I verified with info irq in qemu monitor).
I tried also to hack i8259.c and the function is not called (I think).
What the first parameter of pic_set_irq_new is referred to?

Another question: why a new virtual device works anyway without interrupt
mechanism? isn't it essential?

Thanks

Ale

2006/11/2, Paul Brook <paul@codesourcery.com>:
>
> On Wednesday 01 November 2006 23:25, Roger Lathrop wrote:
> > Alessandro,
> >
> > All you should need to do to raise an IRQ in your code is:
> > pic_set_irq(s->irq,1);
> >
> > When the irq is serviced (in one of your ioport traps, I would assume),
> > knock the irq down:
> > pic_set_irq(s->irq,0);
>
> No. You should use pic_set_irq_new. Otherwise your code will break on
> machines
> with multiple interrupt controllers.
>
> Paul
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>

[-- Attachment #2: Type: text/html, Size: 1470 bytes --]

  parent reply	other threads:[~2006-11-12 15:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200611011205.1gFjwA1qs3Nl3pX2@cave.mail.atl.earthlink.net>
2006-11-01 23:25 ` Re:[Qemu-devel] Interrupt request info Roger Lathrop
2006-11-01 23:31   ` [Qemu-devel] " Paul Brook
2006-11-04 16:08     ` Alessandro Corradi
2006-11-06 14:39       ` Fwd: " Alessandro Corradi
2006-11-11 11:32     ` Alessandro Corradi
2006-11-12 15:46     ` Alessandro Corradi [this message]
2006-10-28  9:36 Alessandro Corradi
2006-10-28 19:01 ` Rob Landley

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=b921df970611120746h79a94c4dnb5faa6b09fdbd12b@mail.gmail.com \
    --to=ale.corradi@gmail.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).