From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751807AbbJCJpU (ORCPT ); Sat, 3 Oct 2015 05:45:20 -0400 Received: from mail-wi0-f182.google.com ([209.85.212.182]:37758 "EHLO mail-wi0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751014AbbJCJpS (ORCPT ); Sat, 3 Oct 2015 05:45:18 -0400 Date: Sat, 3 Oct 2015 11:45:12 +0200 From: Ingo Molnar To: Keith Busch Cc: LKML , x86@kernel.org, linux-pci@vger.kernel.org, Jiang Liu , Thomas Gleixner , Dan Williams , Bjorn Helgaas , Bryan Veal , Ingo Molnar , "H. Peter Anvin" Subject: Re: [RFC PATCHv2] x86/pci: Initial commit for new VMD device driver Message-ID: <20151003094512.GA29104@gmail.com> References: <1443721454-25467-1-git-send-email-keith.busch@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1443721454-25467-1-git-send-email-keith.busch@intel.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Keith Busch wrote: > +config VMDDEV > + depends on PCI && PCI_DOMAINS && PCI_MSI && GENERIC_MSI_IRQ_DOMAIN && IRQ_DOMAIN_HIERARCHY > + tristate "Volume Management Device Driver" > + default N > + select HAVE_VMDDEV > + ---help--- > + Adds support for the Intel Volume Manage Device (VMD). VMD is > + a secondary PCI host bridge that allows PCI Express root ports, > + and devices attached to them, to be removed from the default PCI > + domain and placed within the VMD domain. If your system provides > + one of these and has devices attached to it, say "Y". So what this text does not explain is why does the user care? What tangible benefits does this feature offer to users? Thanks, Ingo