public inbox for linux-ide@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Tejun Heo <tj@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] libata changes for v4.10-rc1
Date: Mon, 12 Dec 2016 11:04:02 -0800	[thread overview]
Message-ID: <20161212190402.GA8592@infradead.org> (raw)
In-Reply-To: <20161212183209.GE13864@htj.duckdns.org>

On Mon, Dec 12, 2016 at 01:32:09PM -0500, Tejun Heo wrote:
> Hello, Linus.
> 
> * Adam added opt-in ATA command priority support.
> 
> * There are machines which hide multiple nvme devices behind an ahci
>   BAR.  Dan Williams proposed a solution to force-switch the mode but
>   deemed too hackishd.  People are gonna discuss the proper way to
>   handle the situation in nvme standard meetings.  For now, detect and
>   warn about the situation.

I wish that was the case.  We've pretty much agreed that we'll want
to implement it as a virtual PCIe root bridge, similar to Intels other
"innovation" VMD that we work around that way.  But Intel management
has apparently decided that they don't want to spend more cycles on
this now that Lenovo has an optional BIOS that doesn't force this
broken mode anymore, and no one outside of Intel has enough information
to implement something like this.

So for now I guess this warning is it, until Intel reconsideres and
spends resources on fixing up the damage their Chipset people caused.

  reply	other threads:[~2016-12-12 19:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-12 18:32 [GIT PULL] libata changes for v4.10-rc1 Tejun Heo
2016-12-12 19:04 ` Christoph Hellwig [this message]
2016-12-12 19:27   ` Tejun Heo
2016-12-13 22:24 ` [GIT PULL UPDATED] " Tejun Heo

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=20161212190402.GA8592@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@kernel.org \
    --cc=torvalds@linux-foundation.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