qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Antonio Caggiano <quic_acaggian@quicinc.com>, qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Peter Xu" <peterx@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH RFC 1/1] memory: Address space map listener
Date: Wed, 5 Apr 2023 16:26:28 +0200	[thread overview]
Message-ID: <f3d172d7-dcdf-1252-13b4-989bfd80f490@redhat.com> (raw)
In-Reply-To: <f72d5432-9300-dfcb-d6b5-0902d67601c6@quicinc.com>

On 05.04.23 16:25, Antonio Caggiano wrote:
> Hi David,
> 
> On 05/04/23 15:23, David Hildenbrand wrote:
>> On 05.04.23 14:57, Antonio Caggiano wrote:
>>> Introduce a MemoryListener callback for address space map events.
>>>
>>
>> Why?
>>
> 
> Please, have a look at the cover letter "[PATCH RFC 0/1] MemoryListener
> address_space_map callback" with a detail explanation of the issue and
> the reason behind this. While I think it solves the issue for my use
> case, it might not be the best or even the right solution for it.

Oh, you did not CC me on the cover letter, so I missed it ...

-- 
Thanks,

David / dhildenb



  reply	other threads:[~2023-04-05 14:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-05 12:57 [PATCH RFC 0/1] MemoryListener address_space_map callback Antonio Caggiano
2023-04-05 12:57 ` [PATCH RFC 1/1] memory: Address space map listener Antonio Caggiano
2023-04-05 13:23   ` David Hildenbrand
2023-04-05 14:25     ` Antonio Caggiano
2023-04-05 14:26       ` David Hildenbrand [this message]
     [not found] <20230405111515.62137-1-quic_acaggian@quicinc.com>
2023-04-05 11:15 ` Antonio Caggiano

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=f3d172d7-dcdf-1252-13b4-989bfd80f490@redhat.com \
    --to=david@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quic_acaggian@quicinc.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).