From: Halil Pasic <pasic@linux.ibm.com>
To: Michael Mueller <mimu@linux.ibm.com>
Cc: Vasily Gorbik <gor@linux.ibm.com>,
Linux-S390 Mailing List <linux-s390@vger.kernel.org>,
Thomas Huth <thuth@redhat.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
KVM Mailing List <kvm@vger.kernel.org>,
Sebastian Ott <sebott@linux.ibm.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Pierre Morel <pmorel@linux.ibm.com>,
Cornelia Huck <cohuck@redhat.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Eric Farman <farman@linux.ibm.com>,
virtualization@lists.linux-foundation.org,
Christoph Hellwig <hch@infradead.org>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Farhan Ali <alifm@linux.ibm.com>,
Viktor Mihajlovski <mihajlov@linux.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>
Subject: Re: [PATCH v3 2/8] s390/cio: introduce DMA pools to cio
Date: Mon, 3 Jun 2019 14:57:30 +0200 [thread overview]
Message-ID: <20190603145730.3e45b8f5.pasic@linux.ibm.com> (raw)
In-Reply-To: <035b4bd3-5856-e8e5-91bf-ba0b5c7c3736@linux.ibm.com>
On Mon, 3 Jun 2019 14:09:02 +0200
Michael Mueller <mimu@linux.ibm.com> wrote:
> >> @@ -224,6 +226,8 @@ struct subchannel *css_alloc_subchannel(struct subchannel_id schid,
> >> INIT_WORK(&sch->todo_work, css_sch_todo);
> >> sch->dev.release = &css_subchannel_release;
> >> device_initialize(&sch->dev);
> >
> > It might be helpful to add a comment why you use 31 bit here...
>
> @Halil, please let me know what comment you prefere here...
>
How about?
/*
* The physical addresses of some the dma structures that
* can belong to a subchannel need to fit 31 bit width (examples ccw,).
*/
> >
> >> + sch->dev.coherent_dma_mask = DMA_BIT_MASK(31);
> >> + sch->dev.dma_mask = &sch->dev.coherent_dma_mask;
> >> return sch;
> >>
> >> err:
> >> @@ -899,6 +903,8 @@ static int __init setup_css(int nr)
> >> dev_set_name(&css->device, "css%x", nr);
> >> css->device.groups = cssdev_attr_groups;
> >> css->device.release = channel_subsystem_release;
> >
> > ...and 64 bit here.
>
> and here.
/*
* We currently allocate notifier bits with this (using css->device
* as the device argument with the DMA API), and are fine with 64 bit
* addresses.
*/
Regards,
Halil
next prev parent reply other threads:[~2019-06-03 12:57 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 12:26 [PATCH v3 0/8] s390: virtio: support protected virtualization Michael Mueller
2019-05-29 12:26 ` [PATCH v3 1/8] s390/mm: force swiotlb for " Michael Mueller
2019-05-29 12:26 ` [PATCH v3 2/8] s390/cio: introduce DMA pools to cio Michael Mueller
2019-06-03 11:37 ` Cornelia Huck
2019-06-03 12:09 ` Michael Mueller
2019-06-03 12:57 ` Halil Pasic [this message]
2019-06-03 13:34 ` Cornelia Huck
2019-06-03 13:43 ` Michael Mueller
2019-06-03 14:04 ` Halil Pasic
2019-06-03 14:22 ` Halil Pasic
2019-06-03 12:47 ` Halil Pasic
2019-06-03 13:40 ` Cornelia Huck
2019-05-29 12:26 ` [PATCH v3 3/8] s390/cio: add basic protected virtualization support Michael Mueller
2019-06-03 12:06 ` Cornelia Huck
2019-06-03 12:45 ` Michael Mueller
2019-06-03 13:42 ` Cornelia Huck
2019-06-03 13:52 ` Michael Mueller
2019-05-29 12:26 ` [PATCH v3 4/8] s390/airq: use DMA memory for adapter interrupts Michael Mueller
2019-06-03 15:27 ` Cornelia Huck
2019-06-04 13:22 ` Halil Pasic
2019-06-04 14:51 ` Cornelia Huck
2019-06-04 15:06 ` Halil Pasic
2019-05-29 12:26 ` [PATCH v3 5/8] virtio/s390: use cacheline aligned airq bit vectors Michael Mueller
2019-06-03 9:10 ` Christian Borntraeger
2019-06-03 15:40 ` Cornelia Huck
2019-05-29 12:26 ` [PATCH v3 6/8] virtio/s390: add indirection to indicators access Michael Mueller
2019-06-03 15:55 ` Cornelia Huck
2019-06-03 17:55 ` Halil Pasic
2019-05-29 12:26 ` [PATCH v3 7/8] virtio/s390: use DMA memory for ccw I/O and classic notifiers Michael Mueller
2019-06-03 16:17 ` Cornelia Huck
2019-06-04 13:08 ` Halil Pasic
2019-06-04 13:36 ` Cornelia Huck
2019-06-04 14:29 ` Halil Pasic
2019-05-29 12:26 ` [PATCH v3 8/8] virtio/s390: make airq summary indicators DMA Michael Mueller
2019-06-03 16:03 ` Cornelia Huck
2019-06-03 17:54 ` Halil Pasic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190603145730.3e45b8f5.pasic@linux.ibm.com \
--to=pasic@linux.ibm.com \
--cc=alifm@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=farman@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hch@infradead.org \
--cc=heiko.carstens@de.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mihajlov@linux.ibm.com \
--cc=mimu@linux.ibm.com \
--cc=mst@redhat.com \
--cc=pmorel@linux.ibm.com \
--cc=sebott@linux.ibm.com \
--cc=thuth@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).