[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <yq138dnexcn.fsf@sermon.lab.mkp.net>
Date: Sat, 26 Jul 2014 15:25:28 -0400
From: "Martin K. Petersen" <martin.petersen@...cle.com>
To: KY Srinivasan <kys@...rosoft.com>
Cc: "Martin K. Petersen" <martin.petersen@...cle.com>,
Sitsofe Wheeler <sitsofe@...il.com>,
Christoph Hellwig <hch@...radead.org>,
"gregkh\@linuxfoundation.org" <gregkh@...uxfoundation.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
"devel\@linuxdriverproject.org" <devel@...uxdriverproject.org>,
"ohering\@suse.com" <ohering@...e.com>,
"apw\@canonical.com" <apw@...onical.com>,
"jasowang\@redhat.com" <jasowang@...hat.com>,
"jbottomley\@parallels.com" <jbottomley@...allels.com>,
"linux-scsi\@vger.kernel.org" <linux-scsi@...r.kernel.org>
Subject: Re: [PATCH v2 3/3] [SCSI] Make LBP quirk skip lbpme checks tests
>>>>> "KY" == KY Srinivasan <kys@...rosoft.com> writes:
>> Great! I'd just like to have a reasonable level of confidence in
>> what's happening down the stack before I entertain turning something
>> on that's not being properly advertised.
KY> As I look at the output of inquiry between Linux on Hyper-V and
KY> native Linux, is not specifying conformance level the main issue?
The main problem for this particular use case (aside from the issue
we've already addressed) is that the passthrough device (SATA SSD) has
LBPME=0 in the READ CAPACITY(16) response. The LBP VPD is correctly
provided with LBPU flag set but because LBPME is reported as disabled we
will not attempt to issue UNMAP commands to the device.
--
Martin K. Petersen Oracle Linux Engineering
--
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/
Powered by blists - more mailing lists