qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kurz <gkurz@linux.vnet.ibm.com>
To: Michael Fritscher <michael@fritscher.net>
Cc: sw@weilnetz.de, aneesh.kumar@linux.vnet.ibm.com, mst@redhat.com,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] [WIP] [RFC ]Add initial 9pfs support for Windows hosts v2
Date: Mon, 4 Sep 2017 10:35:00 +0200	[thread overview]
Message-ID: <20170904103500.23baf790@bahia> (raw)
In-Reply-To: <786fcc685c5e840bf56e3170008eb9a2.squirrel@mifritscher.de>

On Mon, 28 Aug 2017 09:35:45 +0200
"Michael Fritscher" <michael@fritscher.net> wrote:

> Good day,
> 

Hi!

> only a short announcement: Sorry for the very long delay :-( But I'm
> working on this again. The biggest issue seems to be the *at stuff. I'll
> try to workaround this via getting the directories' path from the file
> descriptor with the /proc (as it is already done in the 9pfs_utils) -
> luckily,the mingw environment emulates the /proc. If this doesn't work
> I've another idea (the file descriptors needs to be "registered" with the
> path (and saved in a sparse vector or map with the fd as key and the path
> as value). The "big" solution would be to write a 9p_local_windows.c from
> scratch, but I would like to avoid it.
> 
> Additionally, I changed my approach: Instead of one big patch with
> everything in it, I split it into 2 patch series with several patches:
> 

I'd prefer to have a single series with all the patches because...

>   * The first one only fixes the build via adding #ifdefs, creating stubs
> in os-win32.h etc. and introduces no regressions. Status: Ready in my
> local repo: It compiles fine with enabled 9pfs and works. If 9pfs is
> tried to use there is a clean error message that the fsdev couldn't be
> initialized - as expected.
>   * The second one actually get 9pfs working. This involves mostly
> implementing the *at functions and a few tiny things (O_BINARY and so
> on) Status: Not started yet (will be at the next weekend I hope), but is
> a combination of parts of the the old patch + the implementation of the
> *at functions.
> 
> My hope is that the first series could be merged independently from the
> second. Meanings? If so I'll clean up the first patch series a bit

... I don't want to merge a bunch of code before I'm 100% sure the 9pfs
support on win32 is viable.

Cheers,

--
Greg

> (History cleaning) and send it to the list.
> 
> Best regards,
> Michael Fritscher
> 



-- 
Gregory Kurz                                     kurzgreg@fr.ibm.com
                                                 gkurz@linux.vnet.ibm.com
Software Engineer @ IBM/LTC                      http://www.ibm.com
Tel 33-5-6218-1607

"Anarchy is about taking complete responsibility for yourself."
        Alan Moore.

      reply	other threads:[~2017-09-04  8:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-12  7:52 [Qemu-devel] [PATCH v2] [WIP] [RFC ]Add initial 9pfs support for Windows hosts v2 Michael Fritscher
2016-04-13 12:30 ` Greg Kurz
2016-04-14 19:17 ` Greg Kurz
2016-05-09  8:38 ` Greg Kurz
2016-05-09  9:12   ` Michael Fritscher
2016-05-10 11:26     ` Greg Kurz
2017-08-28  7:35     ` Michael Fritscher
2017-09-04  8:35       ` Greg Kurz [this message]

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=20170904103500.23baf790@bahia \
    --to=gkurz@linux.vnet.ibm.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=michael@fritscher.net \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sw@weilnetz.de \
    /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).