Displaying 3 results from an estimated 3 matches for "function_setting_a_variable".
2019 Jun 04
1
[PATCH v3 7/8] virtio/s390: use DMA memory for ccw I/O and classic notifiers
...Two things:
- The call path goes from the vcdev to the vdev, then back to the vcdev
and then to the cdev. Going from the vcdev to the cdev directly
eliminates the roundtrip via the vdev, which I think does not add
anything.
- I prefer
variable = function_returning_a_pointer(...);
over
function_setting_a_variable(..., variable);
The latter obscures the fact that we change the value of the
variable, unless named very obviously.
>
> I will change this for v4 as you requested. Again sorry for missing it!
np, can happen.
>
> Regards,
> Halil
>
>
> > > if (!thinint_ar...
2019 Jun 03
2
[PATCH v3 7/8] virtio/s390: use DMA memory for ccw I/O and classic notifiers
On Wed, 29 May 2019 14:26:56 +0200
Michael Mueller <mimu at linux.ibm.com> wrote:
> From: Halil Pasic <pasic at linux.ibm.com>
>
> Before virtio-ccw could get away with not using DMA API for the pieces of
> memory it does ccw I/O with. With protected virtualization this has to
> change, since the hypervisor needs to read and sometimes also write these
> pieces of
2019 Jun 03
2
[PATCH v3 7/8] virtio/s390: use DMA memory for ccw I/O and classic notifiers
On Wed, 29 May 2019 14:26:56 +0200
Michael Mueller <mimu at linux.ibm.com> wrote:
> From: Halil Pasic <pasic at linux.ibm.com>
>
> Before virtio-ccw could get away with not using DMA API for the pieces of
> memory it does ccw I/O with. With protected virtualization this has to
> change, since the hypervisor needs to read and sometimes also write these
> pieces of