From: Olaf Hering <olaf@aepfle.de>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: George Dunlap <george.dunlap@cloud.com>,
Jan Beulich <jbeulich@suse.com>,
xen-devel@lists.xenproject.org, Juergen Gross <jgross@suse.com>,
George Dunlap <george.dunlap@citrix.com>
Subject: Re: xentrace buffer size, maxcpus and online cpus
Date: Mon, 19 Jun 2023 12:16:36 +0200 [thread overview]
Message-ID: <20230619121636.672c8cdd.olaf@aepfle.de> (raw)
In-Reply-To: <cab85336-c49f-8993-89ae-a7132c46c0d6@citrix.com>
[-- Attachment #1: Type: text/plain, Size: 428 bytes --]
Fri, 16 Jun 2023 17:08:25 +0100 Andrew Cooper <andrew.cooper3@citrix.com>:
> XENMEM_acquire_resource is a new mapping interface with far more sane
> semantics which, amongst other things, will work in PVH guests too.
Does that indicate xentrace will not work in a PVH dom0?
I will have a look how XENMEM_acquire_resource is used in other places.
The resulting change will likely be too intrusive for 4.18.
Olaf
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-06-19 10:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 7:58 xentrace buffer size, maxcpus and online cpus Olaf Hering
2023-05-30 8:41 ` Jan Beulich
2023-05-30 20:06 ` Olaf Hering
2023-05-31 9:05 ` Jan Beulich
2023-06-16 11:47 ` Olaf Hering
2023-06-16 11:52 ` Jan Beulich
2023-06-16 14:22 ` George Dunlap
2023-06-16 15:37 ` Olaf Hering
2023-06-16 16:08 ` Andrew Cooper
2023-06-19 10:16 ` Olaf Hering [this message]
2023-06-19 11:14 ` Andrew Cooper
2023-06-19 10:13 ` Olaf Hering
2023-06-19 10:22 ` Jan Beulich
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=20230619121636.672c8cdd.olaf@aepfle.de \
--to=olaf@aepfle.de \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=george.dunlap@cloud.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=xen-devel@lists.xenproject.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.