linux-kernel - RE: [PATCH 3/3] drivers:hv: Define the channel type for Hyper-V PCI Express pass-through

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

Message-ID: <BY2PR0301MB16548F0A41E90B7E0D11208FA0460@BY2PR0301MB1654.namprd03.prod.outlook.com>
Date:	Mon, 21 Sep 2015 16:27:28 +0000
From:	KY Srinivasan <kys@...rosoft.com>
To:	Greg KH <gregkh@...uxfoundation.org>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
	"olaf@...fle.de" <olaf@...fle.de>,
	"apw@...onical.com" <apw@...onical.com>,
	"vkuznets@...hat.com" <vkuznets@...hat.com>,
	"jasowang@...hat.com" <jasowang@...hat.com>,
	Jake Oshins <jakeo@...rosoft.com>
Subject: RE: [PATCH 3/3] drivers:hv: Define the channel type for Hyper-V PCI
 Express pass-through



> -----Original Message-----
> From: Greg KH [mailto:gregkh@...uxfoundation.org]
> Sent: Sunday, September 20, 2015 10:29 PM
> To: KY Srinivasan <kys@...rosoft.com>
> Cc: linux-kernel@...r.kernel.org; devel@...uxdriverproject.org;
> olaf@...fle.de; apw@...onical.com; vkuznets@...hat.com;
> jasowang@...hat.com; Jake Oshins <jakeo@...rosoft.com>
> Subject: Re: [PATCH 3/3] drivers:hv: Define the channel type for Hyper-V PCI
> Express pass-through
> 
> On Tue, Sep 15, 2015 at 06:26:49PM -0700, K. Y. Srinivasan wrote:
> > From: Jake Oshins <jakeo@...rosoft.com>
> >
> > This defines the channel type for PCI front-ends in Hyper-V VMs.
> >
> > Signed-off-by: Jake Oshins <jakeo@...rosoft.com>
> > Signed-off-by: K. Y. Srinivasan <kys@...rosoft.com>
> > ---
> >  include/linux/hyperv.h |   11 +++++++++++
> >  1 files changed, 11 insertions(+), 0 deletions(-)
> >
> > diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h
> > index ea0a0e3..5587899 100644
> > --- a/include/linux/hyperv.h
> > +++ b/include/linux/hyperv.h
> > @@ -1140,6 +1140,17 @@ u64 hv_do_hypercall(u64 control, void *input,
> void *output);
> >  		}
> >
> >  /*
> > + * PCI Express Pass Through
> > + * {44C4F61D-4444-4400-9D52-802E27EDE19F}
> > + */
> > +
> > +#define HV_PCIE_GUID \
> > +	.guid = { \
> > +			0x1D, 0xF6, 0xC4, 0x44, 0x44, 0x44, 0x00, 0x44, \
> > +			0x9D, 0x52, 0x80, 0x2E, 0x27, 0xED, 0xE1, 0x9F \
> > +		}
> > +
> > +/*
> >   * Common header for Hyper-V ICs
> >   */
> 
> Yet you do nothing with this, so why add it to the code at this point in
> time?  I can't take pointless things like this...

Greg,

This is a valid GUID that the host can offer us today. The driver to handle this is currently under review (Jake has
posted the code). Traditionally, we have kept our header files in synch with the host functionality.

Regards,

K. Y
--
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/