On 7/2/24 07:39, Andreas Schwab wrote:
On Jul 02 2024, Richard Henderson wrote:
Is /proc mounted in your environment?
Sure, it's a fully running system on real hardware.
I mean, you're not running it in some chroot sandbox without /proc.
r~
On Jul 02 2024, Richard Henderson wrote:
> Is /proc mounted in your environment?
Sure, it's a fully running system on real hardware.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely
https://build.opensuse.org/package/live_build_log/openSUSE:Factory:RISCV/qemu:qemu-linux-user/standard/riscv64
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
On 7/2/24 01:09, Andreas Schwab wrote:
On Jul 01 2024, Richard Henderson wrote:
With -d page, I get
Locating guest address space @ 0x3f4000
Why do you get a different address?
Is /proc mounted in your environment?
The guest address base selection depends on /proc/self/maps.
r~
On 7/2/24 01:09, Andreas Schwab wrote:
On Jul 01 2024, Richard Henderson wrote:
With -d page, I get
Locating guest address space @ 0x3f4000
Why do you get a different address?
Come on, man. Please answer my question:
Now I need to know about your qemu version and build configuration.
Please follow https://en.opensuse.org/openSUSE:RISC-V#QEMU_system_emulation
to start the JeOS-efi image. When logged in:
# zypper rm qemu-linux-user-riscv
# zypper in qemu-linux-user
Then you can run qemu-riscv64 inside:
# qemu-riscv64 -d page hello.riscv64
host mmap_min_addr=0x1
Locating
On Jul 01 2024, Richard Henderson wrote:
> With -d page, I get
>
> Locating guest address space @ 0x3f4000
Why do you get a different address?
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely
Hi Andreas,
Thanks for the test binary.
Now I need to know about your qemu version and build configuration.
Your test binary still works for me. My configuration:
Debian GNU/Linux trixie/sid
gcc version 13.2.0 (Debian 13.2.0-25)
commit 60b4f3aff4e39be04f5d73c65a7e8ef838475c9f (HEAD, tag:
On Thu, 27 Jun 2024 at 15:27, Andreas Schwab wrote:
> Perhaps you should refrain from attacking the volunteers that report
> bugs.
I think the tone of your previous email was extremely
terse and didn't actually answer the question, which is
quite easy to misinterpret as hostility.
We're all
Perhaps you should refrain from attacking the volunteers that report
bugs.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
On Thu, Jun 27, 2024, 1:54 AM Andreas Schwab wrote:
> On Jun 26 2024, Warner Losh wrote:
>
> > On Wed, Jun 26, 2024 at 9:48 AM Richard Henderson <
> > richard.hender...@linaro.org> wrote:
> >
> >> On 6/26/24 01:23, Andreas Schwab wrote:
> >> > On Jun 25 2024, Richard Henderson wrote:
> >> >
> >>
On Jun 26 2024, Warner Losh wrote:
> On Wed, Jun 26, 2024 at 9:48 AM Richard Henderson <
> richard.hender...@linaro.org> wrote:
>
>> On 6/26/24 01:23, Andreas Schwab wrote:
>> > On Jun 25 2024, Richard Henderson wrote:
>> >
>> >> can always force the use of a non-zero base with -B or -R.
>> >
>>
On Wed, Jun 26, 2024 at 9:48 AM Richard Henderson <
richard.hender...@linaro.org> wrote:
> On 6/26/24 01:23, Andreas Schwab wrote:
> > On Jun 25 2024, Richard Henderson wrote:
> >
> >> can always force the use of a non-zero base with -B or -R.
> >
> > $ qemu-riscv64 -d page -B 0x3ee000
On 6/26/24 01:23, Andreas Schwab wrote:
On Jun 25 2024, Richard Henderson wrote:
can always force the use of a non-zero base with -B or -R.
$ qemu-riscv64 -d page -B 0x3ee000 hello.riscv64
host mmap_min_addr=0x1000 (fallback)
qemu-riscv64: /daten/src/test/hello.riscv64: requires virtual
On Jun 25 2024, Richard Henderson wrote:
> can always force the use of a non-zero base with -B or -R.
$ qemu-riscv64 -d page -B 0x3ee000 hello.riscv64
host mmap_min_addr=0x1000 (fallback)
qemu-riscv64: /daten/src/test/hello.riscv64: requires virtual address space
that is in use (omit the -B
On 6/25/24 04:37, Andreas Schwab wrote:
When running qemu-riscv64 on a riscv64 host executing a ET_EXEC riscv64
binary it cannot allocate memory for the stack:
$ qemu-riscv64 -d page ./hello.riscv64
host mmap_min_addr=0x1
Locating guest address space @ 0x3ee000
page layout changed following
When running qemu-riscv64 on a riscv64 host executing a ET_EXEC riscv64
binary it cannot allocate memory for the stack:
$ qemu-riscv64 -d page ./hello.riscv64
host mmap_min_addr=0x1
Locating guest address space @ 0x3ee000
page layout changed following mmap
startend
17 matches
Mail list logo
