On Fri, 16 Jul 2021 at 21:06, Kenneth Adam Miller
wrote:
>
> After checking around, I don't see any _user_ss in any target
> directory. And I only see *_user_ss in the linux-user subdirectory. Were you
> talking about that meson.build in linux-user?
$ git grep _user_ss target
target/i386/meson.
After checking around, I don't see any _user_ss in any target
directory. And I only see *_user_ss in the linux-user subdirectory. Were
you talking about that meson.build in linux-user?
On Fri, Jul 16, 2021 at 1:20 PM Kenneth Adam Miller <
kennethadammil...@gmail.com> wrote:
> Right, that's what I
Right, that's what I was thinking, that I shouldn't be building that for
the system target. That's why I started out with the question that I did,
because I was thinking that it probably hard codes it to user emulation.
Currently though, understanding qemu internals is not so clear to me as I'm
jus
On Fri, 16 Jul 2021 at 18:50, Kenneth Adam Miller
wrote:
> There's a lot of files and I don't want to muddy up the discussion with too
> many details.
If you don't provide details, you get vague answers. Your choice :-)
> And for sure, this is not a problem with the upstream qemu. I'm working o
There's a lot of files and I don't want to muddy up the discussion with too
many details.
And for sure, this is not a problem with the upstream qemu. I'm working on
adding a target, and this is just what I'm experiencing. As for my target,
it has includes that correspond to finds within sub-direct
On Fri, 16 Jul 2021 at 16:16, Kenneth Adam Miller
wrote:
>
> When I go to build the qemu softmmu target the shared files - the i386_ss of
> my arch - gives problems where the build system isn't specifying the include
> headers for the compiler to find the surrounding headers that belong to
> di
When I go to build the qemu softmmu target the shared files - the i386_ss
of my arch - gives problems where the build system isn't specifying the
include headers for the compiler to find the surrounding headers that
belong to different parts of the qemu library. I was able to edit my own
source onl
Oh I didn't know that there was a i386_user_ss in order to see that it was
intended that they were shared that way, so I initially thought that
i386_ss was user only until I saw it in the build.
On Thu, Jul 15, 2021 at 11:35 AM Peter Maydell
wrote:
> On Thu, 15 Jul 2021 at 17:25, Kenneth Adam Mi
On Thu, 15 Jul 2021 at 17:25, Kenneth Adam Miller
wrote:
>
> Well certainly, I know they are different executables. I'm just trying to
> understand how the different targets work.
>
> By subsumes, I mean that just looking at the meson.build for i386, you can
> see that there are files added to t
Well certainly, I know they are different executables. I'm just trying to
understand how the different targets work.
By subsumes, I mean that just looking at the meson.build for i386, you can
see that there are files added to the i386_ss, but not visibly added to the
softmmu target. But the softmm
On Thu, 15 Jul 2021 at 16:59, Kenneth Adam Miller
wrote:
>
> If I am right, the softmmu/system build target for each architecture subsumes
> the source of the user target.
I'm not sure what you mean by "subsumes" here. Some code in
QEMU is compiled into both the system and usermode emulators
(eg
If I am right, the softmmu/system build target for each
architecture subsumes the source of the user target. It's what I see in the
build of i386. But then, I think the user targets have some dedicated user
layer which allow a foreign architecture user binary to be relayed through
in order to map t
12 matches
Mail list logo
