All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Schnelle <svens@stackframe.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-devel@nongnu.org,  deller@gmx.de
Subject: Re: [RFC PATCH] target/hppa: Introduce and use IAQEntry
Date: Tue, 19 Mar 2024 20:37:43 +0100	[thread overview]
Message-ID: <87le6ec8s8.fsf@t14.stackframe.org> (raw)
In-Reply-To: <87plvqc9ub.fsf@t14.stackframe.org> (Sven Schnelle's message of "Tue, 19 Mar 2024 20:14:52 +0100")

Sven Schnelle <svens@stackframe.org> writes:

> Hi Richard,
>
> Richard Henderson <richard.henderson@linaro.org> writes:
>
>> Wrap offset and space into a single structure, with
>> offset represented either as a constant or as variable.
>> This enhances copy_iaoq_entry to copy the space, and at
>> the same time simplifying the code.
>>
>> Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
>> ---
>>
>> Sven, I think this might solve your branch-with-space-change issue.
>> There are a couple of places where it does appear as if we might be
>> losing a space change, with a branch within a branch delay slot.
>> I'm trying to solve this by keeping both queue entries together.
>
> Thanks! I've put that on top of the other changes i have for 64bit
> HP-UX, but it introduces a new problem:
>
>        * Checking configuration for consistency...
> WARNING: The disk at: 10/0/0/0.0.0 (QEMU_QEMU_HARDDISK) appears to contain a 
>          file system and boot area.  Continuing the installation will destroy 
>          any existing data on this disk.
>
>          Do you wish to cancel the non-interactive installation in order to
>          respond to the warnings above? ([y]/n): n
>   
>        * Loading configuration utility...
>        * Beginning installation from source: /dev/dsk/c0t2d0
> =======  03/19/24 13:59:53 EST  Starting system configuration...
>        * Configure_Disks:  Begin
>        * Will install B.11.11 onto this system.
>        * Creating LVM physical volume "/dev/rdsk/c0t0d0" (10/0/0/0.0.0).
>        * Creating volume group "vg00".
> vgcreate: Illegal path "".
>        * Creating logical volume "vg00/lvol1" (/stand).
> lvcreate: Illegal path "".
>        * Creating logical volume "vg00/lvol2" (swap_dump).
> lvcreate: Illegal path "".
>        * Creating logical volume "vg00/lvol3" (/).
> lvcreate: Illegal path "".
>        * Creating logical volume "vg00/lvol4" (/tmp).
> lvcreate: Illegal path "".
>        * Creating logical volume "vg00/lvol5" (/home).
> lvcreate: Illegal path "".
>        * Creating logical volume "vg00/lvol6" (/opt).
> lvcreate: Illegal path "".
>
> The 'illegal path' errors where not present before. I haven't done any
> debugging, as debugging hppa userspace in qemu is a really time
> consuming thing.

I'm seeing the same error with 32bit HP-UX 10.20 - so at least it's not
caused by my 64bit hacks. Linux seems to run fine, but Linux is also
utilizing address spaces not to the same extent as HP-UX.


      reply	other threads:[~2024-03-19 19:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-19 18:33 [RFC PATCH] target/hppa: Introduce and use IAQEntry Richard Henderson
2024-03-19 19:14 ` Sven Schnelle
2024-03-19 19:37   ` Sven Schnelle [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=87le6ec8s8.fsf@t14.stackframe.org \
    --to=svens@stackframe.org \
    --cc=deller@gmx.de \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    /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.