linux-kernel - Re: drivres/hv

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>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20121129101317.4a7ccb8e@pyramind.ukuu.org.uk>
Date:	Thu, 29 Nov 2012 10:13:17 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	KY Srinivasan <kys@...rosoft.com>
Cc:	Greg KH <gregkh@...uxfoundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>
Subject: Re: drivres/hv

> All I know is that it is present and its size is known. If I have a way of knowing
> what range of mmio memory is unclaimed; I could grab that perhaps using
> the request_mem_region() call, I know the size that is reserved for this device.
> So, is there a way to query the system for the first unclaimed address in the mmio
> range.

You can add memory region resources yes. See the code in drivers/pci
which allocates mmio space to unassigned BARs and/or moves stuff around.

Alan
--
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/