WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: Continuing problems booting

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] Re: Continuing problems booting
From: Gerd Hoffmann <kraxel@xxxxxxxxxx>
Date: Tue, 10 Mar 2009 23:00:17 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, M A Young <m.a.young@xxxxxxxxxxxx>
Delivery-date: Tue, 10 Mar 2009 15:01:05 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <49B69FC4.9050204@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <alpine.GSO.2.00.0902201239010.757@xxxxxxxxxxxxxxxx> <alpine.LFD.2.00.0902211225540.14632@xxxxxxxxxxxxxxx> <49A0F68D.9070306@xxxxxxxx> <alpine.LFD.2.00.0902220922040.4149@xxxxxxxxxxxxxxx> <alpine.LFD.2.00.0902221449410.17196@xxxxxxxxxxxxxxx> <49A187B8.7000902@xxxxxxxx> <alpine.LFD.2.00.0902222257230.4472@xxxxxxxxxxxxxxx> <49A1DD80.1080903@xxxxxxxx> <alpine.LFD.2.00.0902222359090.4472@xxxxxxxxxxxxxxx> <49A241EC.3050300@xxxxxxxx> <alpine.LFD.2.00.0902242228550.12607@xxxxxxxxxxxxxxx> <alpine.LFD.2.00.0902272317030.17305@xxxxxxxxxxxxxxx> <49A890FF.4080803@xxxxxxxx> <49ABAF7C.6050906@xxxxxxxxxx> <49AF5FEB.4010508@xxxxxxxx> <49AF80C1.2060307@xxxxxxxxxx> <49AFB122.5040301@xxxxxxxxxx> <49B02069.5000207@xxxxxxxx> <49B12FE4.7050503@xxxxxxxxxx> <49B13F2F.1060100@xxxxxxxx> <49B1426E.3080901@xxxxxxxxxx> <49B14A87.1030504@xxxxxxxx> <49B51796.1050005@xxxxxxxxxx> <49B542D5.1070601@xxxxxxxx> <49B6356D.20603@xxxxxxxxxx> <49B69FC4.9050204@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.19 (X11/20090105)
Jeremy Fitzhardinge wrote:
> Could you s-o-b them too?

Sure.

>> +    if (0 == nr_ioapics) {
>> +        for (irq=0; irq < NR_IRQS_LEGACY; irq++)
>> +            xen_allocate_pirq(irq, "legacy");
>> +        return;
>> +    }
>>   
> 
> I guess the assumption here is that if there's no ioapics, we don't have
> acpi?  Or I guess it doesn't matter because we can't program the
> triggering anyway.

We can't program the trigger anyway.  My machine has acpi.  Nevertheless
acpi_get_override_irq fails due to no ioapic being present.

>>      /* Pre-allocate legacy irqs */
>>      for (irq=0; irq < NR_IRQS_LEGACY; irq++) {
>> -        int trigger, polarity;
>> -
>> -        if (acpi_get_override_irq(irq, &trigger, &polarity) == -1)
>> -            continue;
>> +        int trigger= 1, polarity = 0;
>>  
>> +        acpi_get_override_irq(irq, &trigger, &polarity);
>>          xen_register_gsi(irq,
>>              trigger ? ACPI_LEVEL_SENSITIVE : ACPI_EDGE_SENSITIVE,
>>              polarity ? ACPI_ACTIVE_LOW : ACPI_ACTIVE_HIGH);
> 
> 2: acpi_get_override_irq()
> returns the appropriate default for ISA anyway, and we shouldn't do
> anything if it fails

Ok.  So the old code should be fine and we just need the additional loop
to handle the ioapic-less case.  Will send updated patches tomorrow.

cheers,
  Gerd



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel