From: Igor Mammedov <imammedo@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Peter Xu <peterx@redhat.com>,
qemu-devel@nongnu.org, mst@redhat.com, anisinha@redhat.com,
elena.ufimtseva@oracle.com, jag.raman@oracle.com,
pbonzini@redhat.com, david@redhat.com, philmd@linaro.org
Subject: Re: [PATCH 1/3] memory: reintroduce BQL-free fine-grained PIO/MMIO
Date: Tue, 1 Jul 2025 16:33:33 +0200 [thread overview]
Message-ID: <20250701163333.32364b32@fedora> (raw)
In-Reply-To: <ehnkq6m3mdnrh2my5ui7agknq42js7y2rlu4ghtvj7egscryhg@4g4kapalbj62>
On Mon, 30 Jun 2025 12:02:25 +0200
Gerd Hoffmann <kraxel@redhat.com> wrote:
> Hi,
>
> > As you've said in comment
> > https://bugzilla.redhat.com/show_bug.cgi?id=1322713#c6
> > it's strange that patch causes issues at all, especially with
> > '-smp 1' as in reproducer.
> >
> > Also repeated with -smp x>1, it still worked fine.
> >
> > Perhaps issue was elsewhere after all.
>
> Yea, looks pretty much like this. Guess we do not need the
> 'make only read access lockless' part then.
Yep, I'll ditch readonly and instead add proper fine-grained locking
to PM and HPET timers instead (HPET needs it anyways as Peter pointed out,
while PM will be just a collateral)
>
> take care,
> Gerd
>
next prev parent reply other threads:[~2025-07-01 14:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 15:14 [PATCH 0/3] Reinvent BQL-free PIO/MMIO Igor Mammedov
2025-06-20 15:14 ` [PATCH 1/3] memory: reintroduce BQL-free fine-grained PIO/MMIO Igor Mammedov
2025-06-20 16:53 ` Peter Xu
2025-06-23 12:51 ` Igor Mammedov
2025-06-23 13:36 ` Peter Xu
2025-06-24 7:07 ` Gerd Hoffmann
2025-06-24 10:45 ` Igor Mammedov
2025-06-27 12:02 ` Igor Mammedov
2025-06-30 10:02 ` Gerd Hoffmann
2025-07-01 14:33 ` Igor Mammedov [this message]
2025-06-24 10:57 ` Igor Mammedov
2025-06-20 15:14 ` [PATCH 2/3] acpi: mark PMTIMER as unlocked Igor Mammedov
2025-06-20 15:14 ` [PATCH 3/3] mark HPET " Igor Mammedov
2025-06-20 17:01 ` Peter Maydell
2025-06-24 10:39 ` Igor Mammedov
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=20250701163333.32364b32@fedora \
--to=imammedo@redhat.com \
--cc=anisinha@redhat.com \
--cc=david@redhat.com \
--cc=elena.ufimtseva@oracle.com \
--cc=jag.raman@oracle.com \
--cc=kraxel@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.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.