On Thu, 2012-07-19 at 08:00 +0200, Paolo Bonzini wrote:
Il 18/07/2012 21:12, Anthony Liguori ha scritto:
Windows does this with a points system and I do believe that INQUIRY
responses from any local disks are included in this tally.
INQUIRY responses (at least vendor/product/type) should
Il 19/07/2012 09:28, James Bottomley ha scritto:
INQUIRY responses (at least vendor/product/type) should not change.
INQUIRY responses often change for arrays because a firmware upgrade
enables new features and new features have to declare themselves,
usually in the INQUIRY data. What you
On 07/17/2012 04:50 PM, Nicholas A. Bellinger wrote:
On Tue, 2012-07-17 at 13:55 -0500, Anthony Liguori wrote:
On 07/17/2012 10:05 AM, Michael S. Tsirkin wrote:
On Wed, Jul 11, 2012 at 09:15:00PM +, Nicholas A. Bellinger wrote:
SNIP
It still seems not 100% clear whether this driver
Il 18/07/2012 15:42, Anthony Liguori ha scritto:
If you add support for a new command, you need to provide userspace a
way to disable this command. If you change what gets reported for VPD,
you need to provide userspace a way to make VPD look like what it did in
a previous version.
The QEMU
On Wed, Jul 18, 2012 at 08:42:21AM -0500, Anthony Liguori wrote:
On 07/17/2012 04:50 PM, Nicholas A. Bellinger wrote:
On Tue, 2012-07-17 at 13:55 -0500, Anthony Liguori wrote:
On 07/17/2012 10:05 AM, Michael S. Tsirkin wrote:
On Wed, Jul 11, 2012 at 09:15:00PM +, Nicholas A. Bellinger
On Wed, Jul 18, 2012 at 08:42:21AM -0500, Anthony Liguori wrote:
If you add support for a new command, you need to provide userspace
a way to disable this command. If you change what gets reported for
VPD, you need to provide userspace a way to make VPD look like what
it did in a previous
On Wed, Jul 18, 2012 at 11:53:38AM -0400, Christoph Hellwig wrote:
On Wed, Jul 18, 2012 at 08:42:21AM -0500, Anthony Liguori wrote:
If you add support for a new command, you need to provide userspace
a way to disable this command. If you change what gets reported for
VPD, you need to
On 07/18/2012 10:53 AM, Christoph Hellwig wrote:
On Wed, Jul 18, 2012 at 08:42:21AM -0500, Anthony Liguori wrote:
If you add support for a new command, you need to provide userspace
a way to disable this command. If you change what gets reported for
VPD, you need to provide userspace a way to
On Jul 18, 2012, at 9:00 AM, Michael S. Tsirkin wrote:
On Wed, Jul 18, 2012 at 11:53:38AM -0400, Christoph Hellwig wrote:
On Wed, Jul 18, 2012 at 08:42:21AM -0500, Anthony Liguori wrote:
If you add support for a new command, you need to provide userspace
a way to disable this command. If
On Wed, 2012-07-18 at 11:00 -0500, Anthony Liguori wrote:
On 07/18/2012 10:53 AM, Christoph Hellwig wrote:
On Wed, Jul 18, 2012 at 08:42:21AM -0500, Anthony Liguori wrote:
If you add support for a new command, you need to provide userspace
a way to disable this command. If you change
On Wed, Jul 18, 2012 at 04:42:33PM +, Rustad, Mark D wrote:
On Jul 18, 2012, at 9:00 AM, Michael S. Tsirkin wrote:
On Wed, Jul 18, 2012 at 11:53:38AM -0400, Christoph Hellwig wrote:
On Wed, Jul 18, 2012 at 08:42:21AM -0500, Anthony Liguori wrote:
If you add support for a new
On 07/18/2012 11:47 AM, James Bottomley wrote:
On Wed, 2012-07-18 at 11:00 -0500, Anthony Liguori wrote:
Of course: Think about the consequences: you want to upgrade one array
on your SAN. You definitely don't want to shut down your entire data
centre to achieve it. In place upgrades on
On Jul 18, 2012, at 10:17 AM, Michael S. Tsirkin wrote:
snip
You do have to pay very close attention to some things however. Don't change
the device identity in any way - even version information, otherwise a
Windows initiator will blue-screen. I made that mistake myself, so I
remember it
On Wed, 2012-07-18 at 08:42 -0500, Anthony Liguori wrote:
On 07/17/2012 04:50 PM, Nicholas A. Bellinger wrote:
On Tue, 2012-07-17 at 13:55 -0500, Anthony Liguori wrote:
On 07/17/2012 10:05 AM, Michael S. Tsirkin wrote:
On Wed, Jul 11, 2012 at 09:15:00PM +, Nicholas A. Bellinger wrote:
On Wed, Jul 11, 2012 at 09:15:00PM +, Nicholas A. Bellinger wrote:
From: Nicholas Bellinger n...@linux-iscsi.org
Hi folks,
The following is a RFC-v2 series of tcm_vhost target fabric driver code
currently in-flight for-3.6 mainline code.
After last week's developments along with the
On 07/17/2012 10:05 AM, Michael S. Tsirkin wrote:
On Wed, Jul 11, 2012 at 09:15:00PM +, Nicholas A. Bellinger wrote:
From: Nicholas Bellingern...@linux-iscsi.org
Hi folks,
The following is a RFC-v2 series of tcm_vhost target fabric driver code
currently in-flight for-3.6 mainline code.
On Tue, Jul 17, 2012 at 01:55:42PM -0500, Anthony Liguori wrote:
On 07/17/2012 10:05 AM, Michael S. Tsirkin wrote:
On Wed, Jul 11, 2012 at 09:15:00PM +, Nicholas A. Bellinger wrote:
From: Nicholas Bellingern...@linux-iscsi.org
Hi folks,
The following is a RFC-v2 series of tcm_vhost
On Tue, 2012-07-17 at 18:05 +0300, Michael S. Tsirkin wrote:
On Wed, Jul 11, 2012 at 09:15:00PM +, Nicholas A. Bellinger wrote:
From: Nicholas Bellinger n...@linux-iscsi.org
Hi folks,
The following is a RFC-v2 series of tcm_vhost target fabric driver code
currently in-flight
On Tue, Jul 17, 2012 at 02:17:22PM -0700, Nicholas A. Bellinger wrote:
On Tue, 2012-07-17 at 18:05 +0300, Michael S. Tsirkin wrote:
On Wed, Jul 11, 2012 at 09:15:00PM +, Nicholas A. Bellinger wrote:
From: Nicholas Bellinger n...@linux-iscsi.org
Hi folks,
The following is a
On Tue, 2012-07-17 at 13:55 -0500, Anthony Liguori wrote:
On 07/17/2012 10:05 AM, Michael S. Tsirkin wrote:
On Wed, Jul 11, 2012 at 09:15:00PM +, Nicholas A. Bellinger wrote:
SNIP
It still seems not 100% clear whether this driver will have major
userspace using it. And if not, it
On Tue, Jul 17, 2012 at 02:17:22PM -0700, Nicholas A. Bellinger wrote:
Wrt to staging, I'd like to avoid mucking with staging because:
*) The code has been posted for review
*) The code has been converted to use the latest target-core primitives
*) The code does not require cleanups between
On Wed, 2012-07-18 at 00:34 +0300, Michael S. Tsirkin wrote:
On Tue, Jul 17, 2012 at 02:17:22PM -0700, Nicholas A. Bellinger wrote:
On Tue, 2012-07-17 at 18:05 +0300, Michael S. Tsirkin wrote:
On Wed, Jul 11, 2012 at 09:15:00PM +, Nicholas A. Bellinger wrote:
From: Nicholas Bellinger
On Wed, 2012-07-18 at 00:58 +0300, Michael S. Tsirkin wrote:
On Tue, Jul 17, 2012 at 02:17:22PM -0700, Nicholas A. Bellinger wrote:
Wrt to staging, I'd like to avoid mucking with staging because:
*) The code has been posted for review
*) The code has been converted to use the latest
On Tue, Jul 17, 2012 at 03:02:08PM -0700, Nicholas A. Bellinger wrote:
On Wed, 2012-07-18 at 00:34 +0300, Michael S. Tsirkin wrote:
On Tue, Jul 17, 2012 at 02:17:22PM -0700, Nicholas A. Bellinger wrote:
On Tue, 2012-07-17 at 18:05 +0300, Michael S. Tsirkin wrote:
On Wed, Jul 11, 2012 at
On Wed, 2012-07-18 at 01:18 +0300, Michael S. Tsirkin wrote:
On Tue, Jul 17, 2012 at 03:02:08PM -0700, Nicholas A. Bellinger wrote:
On Wed, 2012-07-18 at 00:34 +0300, Michael S. Tsirkin wrote:
On Tue, Jul 17, 2012 at 02:17:22PM -0700, Nicholas A. Bellinger wrote:
On Tue, 2012-07-17 at
On Tue, Jul 17, 2012 at 03:37:20PM -0700, Nicholas A. Bellinger wrote:
On Wed, 2012-07-18 at 01:18 +0300, Michael S. Tsirkin wrote:
On Tue, Jul 17, 2012 at 03:02:08PM -0700, Nicholas A. Bellinger wrote:
On Wed, 2012-07-18 at 00:34 +0300, Michael S. Tsirkin wrote:
On Tue, Jul 17, 2012 at
On Wed, 2012-07-18 at 02:11 +0300, Michael S. Tsirkin wrote:
On Tue, Jul 17, 2012 at 03:37:20PM -0700, Nicholas A. Bellinger wrote:
On Wed, 2012-07-18 at 01:18 +0300, Michael S. Tsirkin wrote:
On Tue, Jul 17, 2012 at 03:02:08PM -0700, Nicholas A. Bellinger wrote:
On Wed, 2012-07-18 at
From: Nicholas Bellinger n...@linux-iscsi.org
Hi folks,
The following is a RFC-v2 series of tcm_vhost target fabric driver code
currently in-flight for-3.6 mainline code.
After last week's developments along with the help of some new folks, the
changelog v1 - v2 so far looks like:
*) Fix
28 matches
Mail list logo
