From: Kashyap Chamarthy <kchamart@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: aarcange@redhat.com, qemu-devel@nongnu.org, dgilbert@redhat.com,
stefanha@redhat.com, pbonzini@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 13:37:54 +0100 [thread overview]
Message-ID: <20191115123754.GT7754@paraplu> (raw)
In-Reply-To: <f8dce546-ea28-0619-a20a-62c762f99721@redhat.com>
On Fri, Nov 15, 2019 at 01:08:53PM +0100, Thomas Huth wrote:
> On 08/11/2019 10.22, Kashyap Chamarthy wrote:
> > This blog post summarizes the talk "Micro-Optimizing KVM VM-Exits"[1],
> > given by Andrea Arcangeli at the recently concluded KVM Forum 2019.
> >
>
> Hi Kashyap,
>
> first thanks for writing up this article! It's a really nice summary of
> the presentation, I think.
Hi Thomas,
Thanks!
> But before we include it, let me ask a meta-question: Is an article
> about the KVM *kernel* code suitable for the *QEMU* blog?
I had the same thought, and expressed it to Stefan as such, when he
suggested qemu.org :-). I too found it odd to have a kernel-heavy
article on qemu.org.
> Or is there
> maybe a better place for this, like an article on www.linux-kvm.org ?
I thought about it; but I've never seen anyone write an "article" there;
as it's a WikiSpace. And, like Paolo, I couldn't think of a better
place either.
FWIW, the qemu.org blog is indexed by a few blog "planet" aggregators;
and linux-kvm.org is largely a static site that is occasionally updated
by people if they happened to notice something (especially if it's
egregiously wrong).
> 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.)
[...]
--
/kashyap
next prev parent reply other threads:[~2019-11-15 12:43 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 [this message]
2019-11-15 12:41 ` Paolo Bonzini
2019-11-15 15:19 ` Kashyap Chamarthy
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=20191115123754.GT7754@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.