From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: KY Srinivasan <kys@microsoft.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>
Subject: Re: drivres/hv
Date: Thu, 29 Nov 2012 10:13:17 +0000 [thread overview]
Message-ID: <20121129101317.4a7ccb8e@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <426367E2313C2449837CD2DE46E7EAF930E5E599@SN2PRD0310MB382.namprd03.prod.outlook.com>
> 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
next prev parent reply other threads:[~2012-11-29 10:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 20:17 drivres/hv K. Y. Srinivasan
2012-11-28 22:43 ` drivres/hv Greg KH
2012-11-28 23:32 ` drivres/hv KY Srinivasan
2012-11-29 0:04 ` drivres/hv Greg KH
2012-11-29 0:35 ` drivres/hv KY Srinivasan
2012-11-29 10:13 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-11-30 21:15 drivres/hv K. Y. Srinivasan
2016-02-08 6:13 ` drivres/hv Greg KH
2015-08-01 19:46 drivres/hv K. Y. Srinivasan
2015-08-01 18:35 ` drivres/hv Greg KH
2015-08-01 18:39 ` drivres/hv KY Srinivasan
2012-11-02 22:11 drivres/hv K. Y. Srinivasan
2012-11-02 23:37 ` drivres/hv Greg KH
2012-11-03 14:13 ` drivres/hv KY Srinivasan
2012-11-15 22:22 ` drivres/hv KY Srinivasan
2012-11-15 22:34 ` drivres/hv Andrew Morton
2012-11-15 22:42 ` drivres/hv Greg KH
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=20121129101317.4a7ccb8e@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®