public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jake Oshins <jakeo@microsoft.com>
Cc: rafael.j.wysocki@intel.com, kys@microsoft.com,
	linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
	olaf@aepfle.de, apw@canonical.com, vkuznets@redhat.com
Subject: Re: [PATCH 1/3] drivers:pnp Add support for descendants claiming memory address space
Date: Sun, 1 Mar 2015 19:33:49 -0800	[thread overview]
Message-ID: <20150302033349.GA31395@kroah.com> (raw)
In-Reply-To: <1424202111-14461-1-git-send-email-jakeo@microsoft.com>

On Tue, Feb 17, 2015 at 11:41:49AM -0800, Jake Oshins wrote:
> This patch adds some wrapper functions in the pnp layer.  The intent is
> to allow memory address space claims by devices which are descendants
> (a child or grandchild of) a device which is already part of the pnp
> layer.  This allows a device to make a resource claim that doesn't
> conflict with its "aunts" and "uncles."
> 
> This is useful in a Hyper-V VM because some paravirtual "devices" need
> memory-mapped I/O space, and their aunts and uncles can be PCI devices.
> Furthermore, the hypervisor expresses the possible memory address
> combinations for the devices in the VM through the ACPI namespace.
> The paravirtual devices need to suballocate from the ACPI nodes, and
> they need to avoid conflicting with choices that the Linux PCI code
> makes about the PCI devices in the VM.
> 
> It might seem like this should be done in the platform layer rather
> than the pnp layer, but the platform layer assumes that the
> configuration of the devices in the machine are static, or at least
> expressed by firmware in a static fashion.  The nature of a Hyper-V
> VM is that new devices can be added while the machine is running,
> and the potential configurations for them are expressed as part of
> the paravirtual communications channel.  This much more naturally
> aligns with the pnp layer.
> 
> Signed-off-by: Jake Oshins <jakeo@microsoft.com>
> ---
>  drivers/pnp/Makefile     |   2 +-
>  drivers/pnp/base.h       |   2 +
>  drivers/pnp/core.c       |   1 +
>  drivers/pnp/descendant.c | 117 +++++++++++++++++++++++++++++++++++++++++++++++
>  include/linux/pnp.h      |  23 ++++++++++
>  5 files changed, 144 insertions(+), 1 deletion(-)
>  create mode 100644 drivers/pnp/descendant.c

At first glance, this looks ok.  Does it change the sysfs layout of
hyperv devices?

also, I'd like KY to sign-off on it, verifying that he at least tested
the series and it works for him.

thanks,

greg k-h

  parent reply	other threads:[~2015-03-02  3:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-17 19:41 [PATCH 1/3] drivers:pnp Add support for descendants claiming memory address space Jake Oshins
2015-02-17 19:41 ` [PATCH 2/3] drivers:hv Convert VMBus and its descendants to PnP Jake Oshins
2015-02-18 10:24   ` Dan Carpenter
2015-02-18 16:55     ` Jake Oshins
2015-02-17 19:41 ` [PATCH 3/3] drivers:hv Remove old MMIO management code Jake Oshins
2015-03-02  3:33 ` Greg KH [this message]
2015-03-02  3:36   ` [PATCH 1/3] drivers:pnp Add support for descendants claiming memory address space KY Srinivasan
2015-03-05 23:03 ` Rafael J. Wysocki
2015-03-10 22:10   ` Jake Oshins
2015-03-11  0:34     ` Rafael J. Wysocki
2015-03-19 19:21       ` Jake Oshins

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=20150302033349.GA31395@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=apw@canonical.com \
    --cc=devel@linuxdriverproject.org \
    --cc=jakeo@microsoft.com \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olaf@aepfle.de \
    --cc=rafael.j.wysocki@intel.com \
    --cc=vkuznets@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox