All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Gong Su <gongsu@us.ibm.com>
Cc: virtio-fs@redhat.com, Cornelia Huck <cohuck@redhat.com>
Subject: Re: [Virtio-fs] virtio-fs on zLinux (s390x)
Date: Thu, 12 Dec 2019 18:59:00 +0000	[thread overview]
Message-ID: <20191212185900.GE4282@work-vm> (raw)
In-Reply-To: <OFEFF035BA.8C1142AF-ON002584CE.006405E7-852584CE.0067F3AB@notes.na.collabserv.com>

* Gong Su (gongsu@us.ibm.com) wrote:
> 
> 
> Hi Stefan, I'm resending my questions to the list per your request.
> 
> Basically, I'm trying to see if I can get virtio-fs to work on zLinux.
> Following the instructions on https://virtio-fs.gitlab.io/howto-qemu.html I
> was able to compile all the pieces but when I tried to run qemu I realized
> that it needs -numa option which isn't supported on s390x yet.
> 
> I have talked to Christian Borntraeger (whom I worked with on other
> projects before) and he indicated that he had a plan to add -numa support
> for s390x but currently is busy on other things.
> 
> So I'm trying to see if there are other ways for me to go forward without
> having to wait for Christian. I see two options:
> 
> 1. Merge virtiofsd into qemu itself. In the "Interchangeability" section of
> the virtio-fs design page (https://virtio-fs.gitlab.io/design.html), it
> mentioned that "It is also possible to forego vhost-user and emulate the
> virtio-fs device directly inside the hypervisor, although this may result
> in poor isolation and security." Since each guest typically gets its own
> qemu process, maybe this is acceptable for some use cases. In exchange, you
> get the benefit of not having to carve out a chunk of memory from /dev/shm
> (and maybe simpler communication between virtiofsd and qemu).
> 2. Use something other than -numa to share memory between virtiofsd and
> qemu that's supported on zLinux. I'm not entirely familiar with qemu so I
> have no idea whether this is possible or not.

Hi,
  My understanding is that Igor Mammedov (imammedo@redhat.com) has plans
to allow 'shared' to be set on main memory, so we wouldn't need the numa
code.

Dave

> Thanks.

> _______________________________________________
> Virtio-fs mailing list
> Virtio-fs@redhat.com
> https://www.redhat.com/mailman/listinfo/virtio-fs

--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK


  reply	other threads:[~2019-12-12 18:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-12 18:55 [Virtio-fs] virtio-fs on zLinux (s390x) Gong Su
2019-12-12 18:59 ` Dr. David Alan Gilbert [this message]
2019-12-12 19:10   ` Gong Su
2019-12-13 13:17     ` Igor Mammedov
2019-12-13 15:45       ` Gong Su
2019-12-13 10:44   ` Cornelia Huck
2019-12-13 11:02 ` Stefan Hajnoczi
2019-12-13 15:44   ` Gong Su
  -- strict thread matches above, loose matches on Subject: below --
2020-03-17  7:05 Gong Su
2020-03-17  9:41 ` Igor Mammedov
2020-03-17 12:11   ` Dr. David Alan Gilbert
2020-03-18  2:59   ` Gong Su

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=20191212185900.GE4282@work-vm \
    --to=dgilbert@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=gongsu@us.ibm.com \
    --cc=virtio-fs@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.