From: Kashyap Chamarthy <kchamart@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: aarcange@redhat.com, Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org, dgilbert@redhat.com, stefanha@redhat.com,
vkuznets@redhat.com
Subject: Re: [PATCH qemu-web] Add a blog post on "Micro-Optimizing KVM VM-Exits"
Date: Fri, 15 Nov 2019 16:19:26 +0100 [thread overview]
Message-ID: <20191115151926.GU7754@paraplu> (raw)
In-Reply-To: <71a02677-7db7-0ee0-8529-ca59b6bd0ee6@redhat.com>
On Fri, Nov 15, 2019 at 01:41:01PM +0100, Paolo Bonzini wrote:
> On 15/11/19 13:37, Kashyap Chamarthy wrote:
> >> Opinions? Ideas?
> > Another _potential_ venue: Given the topic is kernel space-related, it
> > is likely to fit in with the LWN audience. LWN itself says they
> > generally look for kernel-related articles. Although, I'm aware that
> > there's already a few LWN articles being written on KVM Forum-based
> > talks. (Perhaps once the "KVM Monolithic" patch series merges, this can
> > be reworked into a standalone LWN kernel article — assuming LWN is
> > amenable to it; need to check with LWN.)
>
> Yeah, perhaps later. For now I guess qemu.org is the best.
Sure; others also seem to agree it's okay to be on qemu.org.
--
/kashyap
next prev parent reply other threads:[~2019-11-15 15:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 9:22 [PATCH qemu-web] Add a blog post on "Micro-Optimizing KVM VM-Exits" Kashyap Chamarthy
2019-11-12 9:42 ` Kashyap Chamarthy
2019-11-12 10:37 ` Stefan Hajnoczi
2019-11-15 12:08 ` Thomas Huth
2019-11-15 12:18 ` Paolo Bonzini
2019-11-15 12:25 ` Alex Bennée
2019-11-15 12:33 ` Daniel P. Berrangé
2019-11-15 12:37 ` Kashyap Chamarthy
2019-11-15 12:41 ` Paolo Bonzini
2019-11-15 15:19 ` Kashyap Chamarthy [this message]
2019-11-15 12:45 ` Laszlo Ersek
2019-11-15 15:27 ` Kashyap Chamarthy
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=20191115151926.GU7754@paraplu \
--to=kchamart@redhat.com \
--cc=aarcange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.com \
--cc=vkuznets@redhat.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 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.