mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Keith Busch <keith.busch@intel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Keith Busch <keith.busch@intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	x86@kernel.org, linux-pci@vger.kernel.org,
	Jiang Liu <jiang.liu@linux.intel.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Dan Williams <dan.j.williams@intel.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Bryan Veal <bryan.e.veal@intel.com>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [RFC PATCHv2] x86/pci: Initial commit for new VMD device driver
Date: Mon, 5 Oct 2015 18:03:09 +0000 (UTC)	[thread overview]
Message-ID: <alpine.LNX.2.00.1510051734310.23840@localhost.lm.intel.com> (raw)
In-Reply-To: <20151005164624.GA13737@gmail.com>

On Mon, 5 Oct 2015, Ingo Molnar wrote:
> * Keith Busch <keith.busch@intel.com> wrote:
>> The immediate benefit is that devices on VMD domains do not use resources
>> on the default PCI domain, so we have more than the 256 buses available.
>
> Would be nice to incorporate that information in the help text and in the
> changelog.

Fair enough. Perhaps we thought the "secondary domain" description
implied that information, but maybe we've been doing this too long. :)

Thanks for the feedback.

  reply	other threads:[~2015-10-05 18:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-01 17:44 Keith Busch
2015-10-03  9:45 ` Ingo Molnar
2015-10-05 14:34   ` Keith Busch
2015-10-05 16:46     ` Ingo Molnar
2015-10-05 18:03       ` Keith Busch [this message]
2015-10-04  0:29 ` kbuild test robot
2015-10-06 23:14 ` Bjorn Helgaas
2015-10-07  0:21   ` Keith Busch
2015-10-07 16:04     ` Keith Busch
2015-10-08 13:29       ` Bjorn Helgaas
2015-10-08 13:47     ` Bjorn Helgaas
2015-10-12 21:05   ` Keith Busch

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=alpine.LNX.2.00.1510051734310.23840@localhost.lm.intel.com \
    --to=keith.busch@intel.com \
    --cc=bhelgaas@google.com \
    --cc=bryan.e.veal@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=hpa@zytor.com \
    --cc=jiang.liu@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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
Powered by JetHome