From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9C9B9C282CE for ; Tue, 4 Jun 2019 14:52:01 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 7DC7422CDB for ; Tue, 4 Jun 2019 14:52:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727793AbfFDOwA (ORCPT ); Tue, 4 Jun 2019 10:52:00 -0400 Received: from mx1.redhat.com ([209.132.183.28]:50420 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727586AbfFDOwA (ORCPT ); Tue, 4 Jun 2019 10:52:00 -0400 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 8CA5A30BB367; Tue, 4 Jun 2019 14:51:29 +0000 (UTC) Received: from gondolin (dhcp-192-222.str.redhat.com [10.33.192.222]) by smtp.corp.redhat.com (Postfix) with ESMTP id 5D8F410013D9; Tue, 4 Jun 2019 14:51:22 +0000 (UTC) Date: Tue, 4 Jun 2019 16:51:20 +0200 From: Cornelia Huck To: Halil Pasic Cc: Michael Mueller , KVM Mailing List , Linux-S390 Mailing List , Sebastian Ott , Heiko Carstens , virtualization@lists.linux-foundation.org, "Michael S . Tsirkin" , Christoph Hellwig , Thomas Huth , Christian Borntraeger , Viktor Mihajlovski , Vasily Gorbik , Janosch Frank , Claudio Imbrenda , Farhan Ali , Eric Farman , Pierre Morel Subject: Re: [PATCH v3 4/8] s390/airq: use DMA memory for adapter interrupts Message-ID: <20190604165120.5afdce78.cohuck@redhat.com> In-Reply-To: <20190604152256.158d688c.pasic@linux.ibm.com> References: <20190529122657.166148-1-mimu@linux.ibm.com> <20190529122657.166148-5-mimu@linux.ibm.com> <20190603172740.1023e078.cohuck@redhat.com> <20190604152256.158d688c.pasic@linux.ibm.com> Organization: Red Hat GmbH MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.49]); Tue, 04 Jun 2019 14:52:00 +0000 (UTC) Sender: kvm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org On Tue, 4 Jun 2019 15:22:56 +0200 Halil Pasic wrote: > On Mon, 3 Jun 2019 17:27:40 +0200 > Cornelia Huck wrote: > > Apologies if that already has been answered (and I missed it in my mail > > pile...), but two things had come to my mind previously: > > > > - CHSC... does anything need to be done there? Last time I asked: > > "Anyway, css_bus_init() uses some chscs > > early (before cio_dma_pool_init), so we could not use the pools > > there, even if we wanted to. Do chsc commands either work, or else > > fail benignly on a protected virt guest?" > > Protected virt won't support all CHSC. The supported ones won't requre > use of shared memory. So we are fine. I suppose the supported ones are the sync chscs that use the chsc area as a direct parameter (and therefore are handled similarly to the other I/O instructions that supply a direct parameter)? I don't think we care about async chscs in KVM/QEMU anyway, as we don't even emulate chsc subchannels :) (And IIRC, you don't get chsc subchannels in z/VM guests, either.) > > > - PCI indicators... does this interact with any dma configuration on > > the pci device? (I know pci is not supported yet, and I don't really > > expect any problems.) > > > > It does but, I'm pretty confident we don't have a problem with PCI. IMHO > Sebastian is the guy who needs to be paranoid about this, and he r-b-ed > the respective patches. Just wanted to make sure that this was on the radar. You guys are obviously in a better position than me to judge this :) Anyway, I do not intend to annoy with those questions, it's just hard to get a feel if there are areas that still need care if you don't have access to the documentation for this... if you tell me that you are aware of it and it should work, that's fine for me.