lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:	Thu, 6 Nov 2008 11:18:17 -0800 (PST)
From:	arvind vasudev <arvind_vasudev2000@...oo.com>
To:	linux-kernel@...r.kernel.org, jbarnes@...tuousgeek.org
Subject: Question about allocating resources for a hotplug device

Increasing the scope to include more people.

Thanks,
Arvind.

--- On Wed, 11/5/08, arvind vasudev <arvind_vasudev2000@...oo.com> wrote:

> From: arvind vasudev <arvind_vasudev2000@...oo.com>
> Subject: Question about allocating resources for a hotplug device
> To: linux-pci@...r.kernel.org
> Date: Wednesday, November 5, 2008, 11:43 AM
> Hello,
> 
> I am not sure if this is the right place to ask this
> question, so please let me know if there is another list
> that I should post this on.
> 
> The question is that I am hotpluging a bridge in a slot,
> and plugging in a device behind the bridge. When I do this,
> I can see that the kernel enumerates the bridge and the
> device (assigns bus and device numbers to them), but it
> fails to allocate the memory resource that the new device is
> requesting for 1MB. After tracing the kernel code (version
> 2.6.23), I can see that call to pci_bus_assign_resources()
> fails. In the normal initialization sequence, it appears as
> though the BAR registers of a device have to be initialized
> before the call to pci_bus_assign_resources(), possibly by
> the BIOS.
> 
> How should the BAR registers of the new device be
> initialized in the case of hotplug?
> 
> Thanks,
> Arvind.
> 
> 
> 
>       
> --
> To unsubscribe from this list: send the line
> "unsubscribe linux-pci" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at 
> http://vger.kernel.org/majordomo-info.html


      
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ