From: Fabiano Rosas <farosas@linux.ibm.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>,
Michael Ellerman <mpe@ellerman.id.au>
Cc: linux-kernel@vger.kernel.org, kvm-ppc@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, Paul Mackerras <paulus@ozlabs.org>
Subject: Re: [PATCH kernel] KVM: PPC: Book3S HV: Make unique debugfs nodename
Date: Wed, 01 Sep 2021 15:26:00 +0000 [thread overview]
Message-ID: <87czpsuxkn.fsf@linux.ibm.com> (raw)
In-Reply-To: <87lf4gv0hf.fsf@linux.ibm.com>
Fabiano Rosas <farosas@linux.ibm.com> writes:
> That is why I mentioned creating a hook similar to
> kvm_create_vcpu_debugfs in the common KVM code. kvm_create_vm_debugfs or
> something.
s/kvm/kvm_arch/
WARNING: multiple messages have this Message-ID (diff)
From: Fabiano Rosas <farosas@linux.ibm.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>,
Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
kvm-ppc@vger.kernel.org
Subject: Re: [PATCH kernel] KVM: PPC: Book3S HV: Make unique debugfs nodename
Date: Wed, 01 Sep 2021 12:26:00 -0300 [thread overview]
Message-ID: <87czpsuxkn.fsf@linux.ibm.com> (raw)
In-Reply-To: <87lf4gv0hf.fsf@linux.ibm.com>
Fabiano Rosas <farosas@linux.ibm.com> writes:
> That is why I mentioned creating a hook similar to
> kvm_create_vcpu_debugfs in the common KVM code. kvm_create_vm_debugfs or
> something.
s/kvm/kvm_arch/
WARNING: multiple messages have this Message-ID (diff)
From: Fabiano Rosas <farosas@linux.ibm.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>,
Michael Ellerman <mpe@ellerman.id.au>
Cc: linux-kernel@vger.kernel.org, kvm-ppc@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, Paul Mackerras <paulus@ozlabs.org>
Subject: Re: [PATCH kernel] KVM: PPC: Book3S HV: Make unique debugfs nodename
Date: Wed, 01 Sep 2021 12:26:00 -0300 [thread overview]
Message-ID: <87czpsuxkn.fsf@linux.ibm.com> (raw)
In-Reply-To: <87lf4gv0hf.fsf@linux.ibm.com>
Fabiano Rosas <farosas@linux.ibm.com> writes:
> That is why I mentioned creating a hook similar to
> kvm_create_vcpu_debugfs in the common KVM code. kvm_create_vm_debugfs or
> something.
s/kvm/kvm_arch/
next prev parent reply other threads:[~2021-09-01 15:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 4:13 [PATCH kernel] KVM: PPC: Book3S HV: Make unique debugfs nodename Alexey Kardashevskiy
2021-07-07 4:13 ` Alexey Kardashevskiy
2021-07-07 4:13 ` Alexey Kardashevskiy
2021-07-07 17:48 ` Fabiano Rosas
2021-07-07 17:48 ` Fabiano Rosas
2021-07-07 17:48 ` Fabiano Rosas
2021-07-08 2:22 ` Alexey Kardashevskiy
2021-07-08 2:22 ` Alexey Kardashevskiy
2021-07-08 2:22 ` Alexey Kardashevskiy
2021-08-13 9:50 ` Alexey Kardashevskiy
2021-08-13 9:50 ` Alexey Kardashevskiy
2021-08-13 9:50 ` Alexey Kardashevskiy
2021-08-17 22:20 ` Fabiano Rosas
2021-08-17 22:20 ` Fabiano Rosas
2021-08-17 22:20 ` Fabiano Rosas
2021-08-24 8:37 ` Alexey Kardashevskiy
2021-08-24 8:37 ` Alexey Kardashevskiy
2021-08-24 8:37 ` Alexey Kardashevskiy
2021-09-01 8:43 ` Alexey Kardashevskiy
2021-09-01 14:23 ` Fabiano Rosas
2021-09-01 14:23 ` Fabiano Rosas
2021-09-01 14:23 ` Fabiano Rosas
2021-09-01 15:26 ` Fabiano Rosas [this message]
2021-09-01 15:26 ` Fabiano Rosas
2021-09-01 15:26 ` Fabiano Rosas
2021-09-02 5:31 ` Alexey Kardashevskiy
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=87czpsuxkn.fsf@linux.ibm.com \
--to=farosas@linux.ibm.com \
--cc=aik@ozlabs.ru \
--cc=kvm-ppc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@ozlabs.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.