If the platform is able to power off the scsi device, add a sysfs entry
may_power_off to let user control the may_power_off flag of the device.
This flag will control when the scsi device is runtime suspended, can we
remove power from it(e.g. let it enter D3 cold ACPI device state).
This flag is
In case user's system is broken with ZPODD(either platform or device),
we use this flag to let user disable ZPODD.
A sysfs entry may_power_off is used as the interface to show/store
the scsi device's may_power_off flag.
If 0, we will disable ZPODD; If 1, we will re-enable ZPODD.
The sysfs entry
Add a new flag may_power_off for scsi device, it gives the user a chance
to control when the device is runtime suspended, can we remove its power
if possible.
I'm planning using this flag for sr and sd.
For sr, if user set 0 to may_power_off, we will disable runtime suspend
for ODD, since runtime
Add a new flag may_power_off for scsi device to let user control when
it is runtime suspended, can we remove its power.
This patchset makes the following patch sent previously deprecated:
[PATCH] scsi: sr: add may_power_off flag
http://marc.info/?l=linux-scsi&m=134614323832520&w=2
The patch "scsi
https://bugzilla.kernel.org/show_bug.cgi?id=12759
Alan changed:
What|Removed |Added
Status|NEEDINFO|RESOLVED
Resolution|
On Wed, 2012-08-29 at 06:50 +, Bart Van Assche wrote:
> On 08/29/12 05:12, Dan Williams wrote:
> > John reports:
> > BUG: soft lockup - CPU#2 stuck for 23s! [kworker/u:8:2202]
> > [..]
> > Call Trace:
> > [] scsi_remove_target+0xda/0x1f0
> > [] sas_rphy_remove+0x55/0x60
> > [] sas_rphy
virtio-scsi needs to report LUNs greater than 256 using the "flat"
format. Because the Linux SCSI layer just maps the SCSI LUN to
an u32, without any parsing, these end up in the range from 16640
to 32767. Fix max_lun to account for the possibility that logical
unit numbers are encoded with the "
From: Wang Sen
On a 32-bit guest with virtio-scsi devices and more than 1G physical memory,
QEMU may crash or Linux will fail to boot.
This bug happens when building the sg_list that is eventually put in the
virtqueue.
Each buffer from the original sg_list is added with sg_set_buf, but this wil
James,
This patch seem to be fine. Please consider this patch as Acked-by: "Sreekanth
Reddy"
Regards,
Sreekanth.
> -Original Message-
> From: linux-scsi-ow...@vger.kernel.org [mailto:linux-scsi-
> ow...@vger.kernel.org] On Behalf Of Martin K. Petersen
> Sent: Wednesday, August 29, 2012
James,
This patch seem to be fine. Please consider this patch as Acked-by: "Sreekanth
Reddy"
Regards,
Sreekanth.
> -Original Message-
> From: Alexey Khoroshilov [mailto:khoroshi...@ispras.ru]
> Sent: Tuesday, August 28, 2012 8:08 PM
> To: James E.J. Bottomley
> Cc: Alexey Khoroshilov;
James,
This patch seem to be fine. Please consider this patch as Acked-by: "Sreekanth
Reddy"
Regards,
Sreekanth
> -Original Message-
> From: linux-scsi-ow...@vger.kernel.org [mailto:linux-scsi-
> ow...@vger.kernel.org] On Behalf Of Martin K. Petersen
> Sent: Wednesday, August 29, 2012
Buongiorno, linux-scsi@vger.kernel.org.
La prenotazione e stata confermata.
http://dactam.com/Informazioni/Ordine.zip?acc=linux-scsi@vger.kernel.org
__
id: 34084025
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to
On 08/28/2012 07:54 PM, Paolo Bonzini wrote:
From: Jason Wang
Instead of storing the queue index in transport-specific virtio structs,
this patch moves them to vring_virtqueue and introduces an helper to get
the value. This lets drivers simplify their management and tracing of
virtqueues.
Sign
On 8/26/2012 12:13 AM, Nicholas A. Bellinger wrote:
> On Sun, 2012-08-26 at 00:06 +0530, Naresh Kumar Inna wrote:
>> On 8/25/2012 2:26 AM, Nicholas A. Bellinger wrote:
>>> On Fri, 2012-08-24 at 23:10 +0530, Naresh Kumar Inna wrote:
On 8/24/2012 1:18 AM, Nicholas A. Bellinger wrote:
> On Fr
14 matches
Mail list logo
