On 02/09/2021 00:23, Fabiano Rosas wrote:
Alexey Kardashevskiy writes:
On 24/08/2021 18:37, Alexey Kardashevskiy wrote:
On 18/08/2021 08:20, Fabiano Rosas wrote:
Alexey Kardashevskiy writes:
On 07/07/2021 14:13, Alexey Kardashevskiy wrote:
alternatively move this debugfs stuff und
Fabiano Rosas 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/
Alexey Kardashevskiy writes:
> On 24/08/2021 18:37, Alexey Kardashevskiy wrote:
>>
>>
>> On 18/08/2021 08:20, Fabiano Rosas wrote:
>>> Alexey Kardashevskiy writes:
>>>
On 07/07/2021 14:13, Alexey Kardashevskiy wrote:
>>>
alternatively move this debugfs stuff under the platform-indepe
On 24/08/2021 18:37, Alexey Kardashevskiy wrote:
On 18/08/2021 08:20, Fabiano Rosas wrote:
Alexey Kardashevskiy writes:
On 07/07/2021 14:13, Alexey Kardashevskiy wrote:
alternatively move this debugfs stuff under the platform-independent
directory, how about that?
That's a good idea
On 18/08/2021 08:20, Fabiano Rosas wrote:
Alexey Kardashevskiy writes:
On 07/07/2021 14:13, Alexey Kardashevskiy wrote:
alternatively move this debugfs stuff under the platform-independent
directory, how about that?
That's a good idea. I only now realized we have two separate directori
Alexey Kardashevskiy writes:
> On 07/07/2021 14:13, Alexey Kardashevskiy wrote:
> alternatively move this debugfs stuff under the platform-independent
> directory, how about that?
That's a good idea. I only now realized we have two separate directories
for the same guest:
$ ls /sys/kernel/debu
On 07/07/2021 14:13, Alexey Kardashevskiy wrote:
Currently it is vm-$currentpid which works as long as there is just one
VM per the userspace (99.99% cases) but produces a bunch
of "debugfs: Directory 'vm16679' with parent 'kvm' already present!"
when syzkaller (syscall fuzzer) is running so o
On 08/07/2021 03:48, Fabiano Rosas wrote:
Alexey Kardashevskiy writes:
Currently it is vm-$currentpid which works as long as there is just one
VM per the userspace (99.99% cases) but produces a bunch
of "debugfs: Directory 'vm16679' with parent 'kvm' already present!"
when syzkaller (syscal
Alexey Kardashevskiy writes:
> Currently it is vm-$currentpid which works as long as there is just one
> VM per the userspace (99.99% cases) but produces a bunch
> of "debugfs: Directory 'vm16679' with parent 'kvm' already present!"
> when syzkaller (syscall fuzzer) is running so only one VM is p
Currently it is vm-$currentpid which works as long as there is just one
VM per the userspace (99.99% cases) but produces a bunch
of "debugfs: Directory 'vm16679' with parent 'kvm' already present!"
when syzkaller (syscall fuzzer) is running so only one VM is present in
the debugfs for a given proce
10 matches
Mail list logo
