All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Scharrenberg <pittipatti@web.de>
To: Arun Sharma <arun.sharma@intel.com>
Cc: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>, xen-devel@lists.xensource.com
Subject: Re: [PATCH] pci-ioapic-0502.patch
Date: Thu, 05 May 2005 20:14:25 +0200	[thread overview]
Message-ID: <427A6281.6050405@web.de> (raw)
In-Reply-To: <20050502223534.GA2641@intel.com>

Hi!

Ah great! I've been looking forward to that patch for some time now  :-) 
Unfortunately it isn't working on my machine. :-/

xen boots, but dom0 freezes while loading the sata-driver.
It is the "silicon image" sata-driver from the scsi-section in
kernel-config.
The system freezes after the line "applying Seagate errata fix" (there
are some issuse between silicon image and seagate)

There exist another driver for that controller in the ATA-section.
When using this driver the system does not freeze, but stops at
sata-driver-loading as well.
But here after some time I get a "lost interrupt" message.

When booting without your patch the sata-controller uses irg 5 and
shares it with 7 other pci-devices.
With your patch the controller uses irq 18, so io-apic is used.

The system is an amd duron with nforce2 chipset.

patrick



Arun Sharma schrieb:

>>Move PCI device scanning to dom0. Enable ACPI in dom0. This should greatly
>>reduce the complexity of xen and move the complexity of dealing with
>>hardware bugs and workarounds etc to dom0.
>>
>>The ioapic local apic (and hence all the vectors) are owned by the hypervisor.
>>Dom0 enables the ACPI interpreter, handles PCI and ACPI based interrupt 
>>routing. 
>>
>>New hypercalls to assign vectors and for accessing the ioapic.
>>
>>Functionality not yet provided:
>>
>>o acpi=off to support machines with broken or no acpi support.
>>o support for driver domains 
>>
>>  
>>
>  
>

  parent reply	other threads:[~2005-05-05 18:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-02 22:35 [PATCH] pci-ioapic-0502.patch Arun Sharma
2005-05-03 20:58 ` Anthony Liguori
2005-05-03 21:14   ` Arun Sharma
2005-05-03 21:24     ` Anthony Liguori
2005-05-03 21:43       ` Arun Sharma
2005-05-03 22:17         ` Anthony Liguori
2005-05-05 18:14 ` Patrick Scharrenberg [this message]
2005-05-05 18:36   ` Arun Sharma
2005-05-06  6:53     ` Patrick Scharrenberg
2005-05-06 20:41     ` Patrick Scharrenberg
2005-05-06 21:00       ` Keir Fraser
2005-05-06 21:17         ` Jonathan S. Shapiro
  -- strict thread matches above, loose matches on Subject: below --
2005-05-04 18:33 Puthiyaparambil, Aravindh
2005-05-04 19:00 ` Keir Fraser
2005-05-04 20:08 ` Arun Sharma
2005-05-05  1:31 ` Arun Sharma

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=427A6281.6050405@web.de \
    --to=pittipatti@web.de \
    --cc=Ian.Pratt@cl.cam.ac.uk \
    --cc=arun.sharma@intel.com \
    --cc=xen-devel@lists.xensource.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.