Date: Sun, 9 May 2021 05:55:42 +0200 From: Daniel Nebdal <dnebdal@gmail.com> Cc: Current <freebsd-current@freebsd.org> Subject: Re: WSLg update on 1-5-2021 - BSD / WSL Message-ID: <CA%2Bt49PJ5pxU_Y3-p3u=bwiRn1AST9isjaSYUB=-NdRCXYLMKJA@mail.gmail.com> In-Reply-To: <92a81582-7bd4-b9f1-04b6-cbcd5eb77893@FreeBSD.org> References: <CAA-K0n%2BsJ%2BKmc3LitPiX_RLxcKv8aUcY9=cRiM7mx58NY5xs-A@mail.gmail.com> <0b3d6049-f6eb-f9d4-5f20-f09ac666e949@nomadlogic.org> <92a81582-7bd4-b9f1-04b6-cbcd5eb77893@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 6 May 2021 at 19:05, David Chisnall <theraven@freebsd.org> wrote: > [ Disclaimer: I work for Microsoft, but not on WSL and this is my own > opinion ] > (...) > David > Just as a counterpoint to Rozhuk's take, that all sounds sensible enough to me - FreeBSD would probably gain more from this than MS. So the WSL2 TODO would be something like this: * Ballooning driver. Seems like a proof of concept would be doable enough - could you model it as an unkillable task (userland or kernel) that wants to allocate a lot of memory, and anything it gets it hands back to the host? * Some sort of boot support. Maybe as a shim that chainloads an unmodified kernel? Probably finicky, but also self-contained. * File systems. Is / also 9p-over-HyperV-channels? If so that's kind of crucial and perhaps the hardest part. Oh, and how does the terminal work? You support multiple ttys, so I guess it's not straight emulated serial? -- Daniel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2Bt49PJ5pxU_Y3-p3u=bwiRn1AST9isjaSYUB=-NdRCXYLMKJA>