From: Greg Kurz <groug@kaod.org>
To: Michael Fritscher <michael@fritscher.net>
Cc: sw@weilnetz.de, aneesh.kumar@linux.vnet.ibm.com, mst@redhat.com,
qemu-devel@nongnu.org, Greg Kurz <gkurz@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] Make 9pfs buildable for Windows
Date: Mon, 6 Nov 2017 14:29:41 +0100 [thread overview]
Message-ID: <20171106142941.2a555646@bahia> (raw)
In-Reply-To: <20170929111323.6308-1-michael@fritscher.net>
On Fri, 29 Sep 2017 13:13:05 +0200
Michael Fritscher <michael@fritscher.net> wrote:
> Good day,
>
Hi,
Sorry for the late reply... Since I have only limited bandwidth, I'll only
be able to provide some limited feedback.
A global remark to start with: it is a usual practice to prefix each patch
title with the component's name, as explained here:
https://wiki.qemu.org/Contribute/SubmitAPatch#Write_a_meaningful_commit_message
eg, patch titles in this series should start with something like with fsdev: or
9pfs: or oslib-win32:
> this is the patch series to make 9pfs buildable (not working!) on Windows.
> It is compiling and starts, but obvousily 9pfs is not working - in fact it
> spits out a initializing error.
>
What's the error message ?
> Next step: Implement the directory and file handling stuff.
>
> Quoting myself:
>
> "
> 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.
> "
>
> I know that some people want to have compiling and working together, but I
> hope(!) that I get a first working version next week.
>
Any updates ? Not sure people will spend time reviewing this series until
something actually works.
> Best regards,
> Michael Fritscher
>
Cheers,
--
Greg
PS: if you repost, please use my maintainer's email address groug@kaod.org
next prev parent reply other threads:[~2017-11-06 13:29 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-29 11:13 [Qemu-devel] Make 9pfs buildable for Windows Michael Fritscher
2017-09-29 11:13 ` [Qemu-devel] [PATCH 01/18] Add definitions needed by file-op-9p.h " Michael Fritscher
2017-11-06 13:34 ` Greg Kurz
2017-09-29 11:13 ` [Qemu-devel] [PATCH 02/18] #include <sys/vfs.h> is not available under Windows Michael Fritscher
2017-11-06 14:27 ` Paolo Bonzini
2017-09-29 11:13 ` [Qemu-devel] [PATCH 03/18] Disable the proxy fsdev " Michael Fritscher
2017-11-06 13:44 ` Greg Kurz
2017-11-06 15:17 ` Michael Fritscher
2017-11-06 16:51 ` Greg Kurz
2017-09-29 11:13 ` [Qemu-devel] [PATCH 04/18] Don't include sys/resource.h on Windows Michael Fritscher
2017-11-06 14:27 ` Paolo Bonzini
2017-09-29 11:13 ` [Qemu-devel] [PATCH 05/18] Add definitions for 9p.c Michael Fritscher
2017-09-29 11:13 ` [Qemu-devel] [PATCH 06/18] Stub out functions for 9pfs Michael Fritscher
2017-09-29 11:13 ` [Qemu-devel] [PATCH 07/18] Fix unused variable error and unsuded function if FS_IOC_GETVERSION is not defined Michael Fritscher
2017-11-06 14:29 ` Paolo Bonzini
2017-09-29 11:13 ` [Qemu-devel] [PATCH 08/18] Stub 9pfs xattr functions for Windows Michael Fritscher
2017-09-29 11:13 ` [Qemu-devel] [PATCH 09/18] Dont initialize fields which aren't available on Windows Michael Fritscher
2017-11-06 14:26 ` Paolo Bonzini
2017-09-29 11:13 ` [Qemu-devel] [PATCH 10/18] dirent has no d_off " Michael Fritscher
2017-09-29 11:13 ` [Qemu-devel] [PATCH 11/18] Sete ctx->xops to null " Michael Fritscher
2017-11-06 14:25 ` Paolo Bonzini
2017-09-29 11:13 ` [Qemu-devel] [PATCH 12/18] Buildfix in 9p-util.c Michael Fritscher
2017-11-06 14:21 ` Paolo Bonzini
2017-09-29 11:13 ` [Qemu-devel] [PATCH 13/18] fsetxattrat_nofollow doesn't seem to be defined on Windows - disable it Michael Fritscher
2017-09-29 11:13 ` [Qemu-devel] [PATCH 14/18] Disable rlimit under Windows Michael Fritscher
2017-11-06 14:24 ` Paolo Bonzini
2017-09-29 11:13 ` [Qemu-devel] [PATCH 15/18] Fix unavailable fields in stbuf " Michael Fritscher
2017-11-06 14:36 ` Paolo Bonzini
2017-11-06 15:23 ` Michael Fritscher
2017-11-06 15:25 ` Paolo Bonzini
2017-09-29 11:13 ` [Qemu-devel] [PATCH 16/18] Workaround for missing dent->d_type/d_off " Michael Fritscher
2017-11-06 14:32 ` Paolo Bonzini
2017-09-29 11:13 ` [Qemu-devel] [PATCH 17/18] Compile fixes for Windows Michael Fritscher
2017-09-29 11:13 ` [Qemu-devel] [PATCH 18/18] Enable 9pfs for Windows in configure / makefiles Michael Fritscher
2017-09-29 12:01 ` [Qemu-devel] Make 9pfs buildable for Windows Paolo Bonzini
2017-09-29 14:14 ` Michael Fritscher
2017-09-29 14:25 ` Paolo Bonzini
2017-09-29 18:09 ` Michael Fritscher
2017-10-01 16:17 ` Michael Fritscher
2017-10-15 19:02 ` Michael Fritscher
2017-10-15 19:13 ` Michael Fritscher
2017-10-15 19:50 ` Greg Kurz
2017-10-15 20:00 ` Michael Fritscher
2017-10-16 5:31 ` Michael Fritscher
2017-10-15 19:45 ` Greg Kurz
2017-11-06 13:29 ` Greg Kurz [this message]
2017-11-06 15:14 ` Michael Fritscher
2017-11-06 15:36 ` Paolo Bonzini
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=20171106142941.2a555646@bahia \
--to=groug@kaod.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=gkurz@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 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.