All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: [PATCH] [ACPI] Enable direct GSI mapping for APIC
Date: Fri, 2 May 2008 12:35:38 -0300	[thread overview]
Message-ID: <20080502153538.GA12124@dmt> (raw)
In-Reply-To: <481B2B5C.50602@suse.de>

On Fri, May 02, 2008 at 04:55:24PM +0200, Alexander Graf wrote:
> Hi,
> 
> in the DSDT there are two different ways of defining, how an interrupt 
> is supposed to be routed. Currently we are using the LNKA - LNKD method, 
> which afaict is for legacy support.
> The other method is to directly tell the Operating System, which APIC 
> pin the device is attached to. We can get that information from the very 
> same entry, the LNKA to LNKD pseudo devices receive it.
> 
> For now this does not give any obvious improvement. It does leave room 
> for more advanced mappings, with several IOAPICs that can handle more 
> devices separately. This might help when we have a lot of devices, as 
> currently all devices sit on two interrupt lanes.
> 
> More importantly (for me) though, is that Darwin enables the APIC mode 
> unconditionally, so it won't easily run in legacy mode.

Hi Alexander,

I'm just about to resend the patchset to add 3 PCI bridges, which
already adds the _SUN method appropriately. Please rebase the APRT patch
on top of that.

Thanks!

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

  reply	other threads:[~2008-05-02 15:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-02 14:55 [PATCH] [ACPI] Enable direct GSI mapping for APIC Alexander Graf
2008-05-02 15:35 ` Marcelo Tosatti [this message]
2008-05-03 20:29   ` Alexander Graf
2008-05-07 10:20 ` Avi Kivity

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=20080502153538.GA12124@dmt \
    --to=mtosatti@redhat.com \
    --cc=agraf@suse.de \
    --cc=kvm-devel@lists.sourceforge.net \
    /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.