On Thu, May 30, 2019 at 7:28 PM Paolo Bonzini wrote:
>
> Adding the command and kicking the virtqueue so far was done one after
> another. Make the kick optional, so that we can take into account SCMD_LAST.
> We also need a commit_rqs callback to kick the device if blk-mq aborts
> the submission
On 5/30/19 1:28 PM, Paolo Bonzini wrote:
> Adding the command and kicking the virtqueue so far was done one after
> another. Make the kick optional, so that we can take into account SCMD_LAST.
> We also need a commit_rqs callback to kick the device if blk-mq aborts
> the submission before the last
On 30/05/19 19:28, Bart Van Assche wrote:
> On 5/30/19 4:28 AM, Paolo Bonzini wrote:
>> @@ -531,7 +547,8 @@ static int virtscsi_queuecommand(struct Scsi_Host
>> *shost,
>> req_size = sizeof(cmd->req.cmd);
>> }
>> - ret = virtscsi_kick_cmd(req_vq, cmd, req_size,
>> sizeof(cmd->r
On 5/30/19 4:28 AM, Paolo Bonzini wrote:
@@ -531,7 +547,8 @@ static int virtscsi_queuecommand(struct Scsi_Host *shost,
req_size = sizeof(cmd->req.cmd);
}
- ret = virtscsi_kick_cmd(req_vq, cmd, req_size, sizeof(cmd->resp.cmd));
+ kick = (sc->flags & SCMD_LAST) !=
Adding the command and kicking the virtqueue so far was done one after
another. Make the kick optional, so that we can take into account SCMD_LAST.
We also need a commit_rqs callback to kick the device if blk-mq aborts
the submission before the last request is reached.
Suggested-by: Stefan Hajnoc
5 matches
Mail list logo