All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: George Dunlap <george.dunlap@cloud.com>
Cc: 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: Fri, 16 Jun 2023 17:37:17 +0200	[thread overview]
Message-ID: <20230616173717.3f264151.olaf@aepfle.de> (raw)
In-Reply-To: <CA+zSX=Y6yrkA0RM0FAM7Cjv2f-UP8FvMUsoRXbMAxP+fNNC79g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 389 bytes --]

Fri, 16 Jun 2023 15:22:24 +0100 George Dunlap <george.dunlap@cloud.com>:

> I agree; the clear implication is that with smt=0, you might have
> num_online_cpus() return 4, but cpuids that look like {1, 3, 5, 7}; so you
> need the trace buffer array to be of size 8.

I see. Apparently some remapping is required to map a cpuid to an index
into the trace buffer metadata.


Olaf

[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-06-16 15:38 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 [this message]
2023-06-16 16:08               ` Andrew Cooper
2023-06-19 10:16                 ` Olaf Hering
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=20230616173717.3f264151.olaf@aepfle.de \
    --to=olaf@aepfle.de \
    --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.