From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Mueller Subject: Re: [PATCH v2 8/8] virtio/s390: make airq summary indicators DMA Date: Tue, 28 May 2019 16:58:11 +0200 Message-ID: References: <20190523162209.9543-1-mimu@linux.ibm.com> <20190523162209.9543-9-mimu@linux.ibm.com> <20190527140018.7c2d34ff.cohuck@redhat.com> <20190528163342.335eea0b.pasic@linux.ibm.com> Reply-To: mimu@linux.ibm.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20190528163342.335eea0b.pasic@linux.ibm.com> Content-Language: en-US List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.linux-foundation.org Errors-To: virtualization-bounces@lists.linux-foundation.org To: Halil Pasic , Cornelia Huck Cc: Vasily Gorbik , Linux-S390 Mailing List , Thomas Huth , Claudio Imbrenda , KVM Mailing List , Sebastian Ott , "Michael S . Tsirkin" , Pierre Morel , Farhan Ali , Heiko Carstens , Eric Farman , virtualization@lists.linux-foundation.org, Christoph Hellwig , Christian Borntraeger , Viktor Mihajlovski , Janosch Frank List-Id: virtualization@lists.linuxfoundation.org On 28.05.19 16:33, Halil Pasic wrote: > On Mon, 27 May 2019 14:00:18 +0200 > Cornelia Huck wrote: > >> On Thu, 23 May 2019 18:22:09 +0200 >> Michael Mueller wrote: >> >>> From: Halil Pasic >>> >>> Hypervisor needs to interact with the summary indicators, so these >>> need to be DMA memory as well (at least for protected virtualization >>> guests). >>> >>> Signed-off-by: Halil Pasic >>> --- >>> drivers/s390/virtio/virtio_ccw.c | 22 +++++++++++++++------- >>> 1 file changed, 15 insertions(+), 7 deletions(-) >> >> (...) >> >>> @@ -1501,6 +1508,7 @@ static int __init virtio_ccw_init(void) >>> { >>> /* parse no_auto string before we do anything further */ >>> no_auto_parse(); >>> + summary_indicators = cio_dma_zalloc(MAX_AIRQ_AREAS); >> >> What happens if this fails? > > Bad things could happen! > > How about adding > > if (!summary_indicators) > virtio_ccw_use_airq = 0; /* fall back to classic */ > > ? > > Since it ain't very likely to happen, we could also just fail > virtio_ccw_init() with -ENOMEM. That is what I'm currently doing in v3. > > Regards, > Halil > > >> >>> return ccw_driver_register(&virtio_ccw_driver); >>> } >>> device_initcall(virtio_ccw_init); >> > Michael