On Fri, Oct 15, 2021 at 11:27:02AM +0200, David Hildenbrand (da...@redhat.com)
wrote:
>
>
> On 15.10.21 11:10, david.dai wrote:
> > On Wed, Oct 13, 2021 at 10:33:39AM +0200, David Hildenbrand
> > (da...@redhat.com) wrote:
> >>
> >> CAUTION: This email originated from outside of the
On 15.10.21 11:10, david.dai wrote:
> On Wed, Oct 13, 2021 at 10:33:39AM +0200, David Hildenbrand
> (da...@redhat.com) wrote:
>>
>> CAUTION: This email originated from outside of the organization. Do not
>> click links or open attachments unless you recognize the sender and know the
>> content is
On Wed, Oct 13, 2021 at 10:33:39AM +0200, David Hildenbrand (da...@redhat.com)
wrote:
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know the
> content is safe.
>
>
> On 13.10.21 10:13, david.dai
On 13.10.21 10:13, david.dai wrote:
On Mon, Oct 11, 2021 at 09:43:53AM +0200, David Hildenbrand (da...@redhat.com)
wrote:
virito-mem currently relies on having a single sparse memory region (anon
mmap, mmaped file, mmaped huge pages, mmap shmem) per VM. Although we can
share memory with
On Mon, Oct 11, 2021 at 09:43:53AM +0200, David Hildenbrand (da...@redhat.com)
wrote:
>
>
>
> > > virito-mem currently relies on having a single sparse memory region (anon
> > > mmap, mmaped file, mmaped huge pages, mmap shmem) per VM. Although we can
> > > share memory with other processes,
virito-mem currently relies on having a single sparse memory region (anon
mmap, mmaped file, mmaped huge pages, mmap shmem) per VM. Although we can
share memory with other processes, sharing with other VMs is not intended.
Instead of actually mmaping parts dynamically (which can be quite
On Thu, Sep 30, 2021 at 12:33:30PM +0200, David Hildenbrand (da...@redhat.com)
wrote:
>
>
> On 30.09.21 11:40, david.dai wrote:
> > On Wed, Sep 29, 2021 at 11:30:53AM +0200, David Hildenbrand
> > (da...@redhat.com) wrote:
> > >
> > > On 27.09.21 14:28, david.dai wrote:
> > > > On Mon, Sep 27,
On 30.09.21 11:40, david.dai wrote:
On Wed, Sep 29, 2021 at 11:30:53AM +0200, David Hildenbrand (da...@redhat.com)
wrote:
On 27.09.21 14:28, david.dai wrote:
On Mon, Sep 27, 2021 at 11:07:43AM +0200, David Hildenbrand (da...@redhat.com)
wrote:
CAUTION: This email originated from outside
On Wed, Sep 29, 2021 at 11:30:53AM +0200, David Hildenbrand (da...@redhat.com)
wrote:
>
> On 27.09.21 14:28, david.dai wrote:
> > On Mon, Sep 27, 2021 at 11:07:43AM +0200, David Hildenbrand
> > (da...@redhat.com) wrote:
> > >
> > > CAUTION: This email originated from outside of the
On 27.09.21 14:28, david.dai wrote:
On Mon, Sep 27, 2021 at 11:07:43AM +0200, David Hildenbrand (da...@redhat.com)
wrote:
CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know the
content is safe.
On
On Mon, Sep 27, 2021 at 11:07:43AM +0200, David Hildenbrand (da...@redhat.com)
wrote:
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know the
> content is safe.
>
>
> On 27.09.21 10:27, Stefan
On Mon, Sep 27, 2021 at 10:27:06AM +0200, Stefan Hajnoczi (stefa...@redhat.com)
wrote:
> On Sun, Sep 26, 2021 at 10:16:14AM +0800, David Dai wrote:
> > Add a virtual pci to QEMU, the pci device is used to dynamically attach
> > memory
> > to VM, so driver in guest can apply host memory in fly
On 27.09.21 10:27, Stefan Hajnoczi wrote:
On Sun, Sep 26, 2021 at 10:16:14AM +0800, David Dai wrote:
Add a virtual pci to QEMU, the pci device is used to dynamically attach memory
to VM, so driver in guest can apply host memory in fly without virtualization
management software's help, such as
On Sun, Sep 26, 2021 at 10:16:14AM +0800, David Dai wrote:
> Add a virtual pci to QEMU, the pci device is used to dynamically attach memory
> to VM, so driver in guest can apply host memory in fly without virtualization
> management software's help, such as libvirt/manager. The attached memory is
Add a virtual pci to QEMU, the pci device is used to dynamically attach memory
to VM, so driver in guest can apply host memory in fly without virtualization
management software's help, such as libvirt/manager. The attached memory is
isolated from System RAM, it can be used in heterogeneous memory
15 matches
Mail list logo