search for: frediano

From: Frediano Ziglio <frediano.ziglio@citrix.com> Split coverage informations extracted from xencov utility. This script accept coverage blob either as file or from input and extract into files compatible with gcc format (gcda). Signed-off-by: Frediano Ziglio <frediano.ziglio@citrix.com> --- tools...

Couple of patches to fix an overflow, optimize a bit and support bigger resolutions using Windows 8.

This patches add support for dynamic sectors to GPT MBR code. First 3 patches are trick and optimizations to gain some space for the forth patch. I have a modified version of SeaBIOS, some code and some script o test it I'll send on a different mail.

Check if some pointers are not NULL due to read errors or other problems Signed-off-by: Frediano Ziglio <frediano.ziglio at citrix.com> --- core/fs/ext2/ext2.c | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/core/fs/ext2/ext2.c b/core/fs/ext2/ext2.c index bddde8d..8f0f2a4 100644 --- a/core/fs/ext2/ext2.c +++ b/core/fs/ext2/ext2.c @@ -139,6 +139,8 @@ ext2_get_...

These patch update Windows generation ID support on ACPI. First patch mainly update to new specifications while second one introduce again the device in ACPI table. Frediano Ziglio (2): genid: Update Windows generation ID genid: Introduce again Windows generation ID device docs/misc/xenstore-paths.markdown | 6 ++++ tools/firmware/hvmloader/acpi/build.c | 49 ++++++++++++++++++++++---------- tools/firmware/hvmloader/acpi/dsdt.asl | 25 +++++++++++++++...

...Does this make sense or is it impossible ?? Also note that rdexact (xc_domain_restore.c) handle data timeout but we can still block in read_exact called by xc_tmem_restore/xc_tmem_restore_extra. Last note on rdexact, isn''t 1 second (HEARTBEAT_MS) too small if there are network problems? Frediano

Signed-off-by: Frediano Ziglio <frediano.ziglio at citrix.com> --- com32/mboot/mboot.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/com32/mboot/mboot.c b/com32/mboot/mboot.c index 35450e0..10e6701 100644 --- a/com32/mboot/mboot.c +++ b/com32/mboot/mboot.c @@ -198,7 +198,7 @@ int main(in...

...ession problems with normal disks. Now I would like to update these patches and upstream them. It's not clear however which is the branch I should use to rebase these patches. Previous patches was against syslinux-4.06 but now there is syslinux-5.01 (elflink) and syslinux-6.00-pre4 (firmware). Frediano

...er that too and therefore disturb qxl operation. So aquire the legacy vga ioports from vgaarb to avoid that. Reproducer: Boot kvm guest with both qxl and i915 vgpu, with qxl being first in pci scan order. v2: Skip this for secondary qxl cards which don't have vga mode in the first place (Frediano). Cc: Frediano Ziglio <fziglio at redhat.com> Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/qxl/qxl_drv.c | 20 +++++++++++++++++++- 1 file changed, 19 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/qxl/qxl_drv.c b/drivers/gpu/drm/qxl/qxl_drv.c in...

On 12/16/2013 05:18 AM, Frediano Ziglio wrote: > > Surely should apply to 4.xx where they was developed but I think I send > them for 5.xx. mbr part of patches was merged time ago. > Unfortunately I had no time to update other patches. If I remember there > was a problem on the way ADV was implemented (using the sa...

Am 27.09.19 um 18:31 schrieb Frediano Ziglio: >> The ttm_mem_io_* functions are actually internal to TTM and shouldn't be >> used in a driver. >> > As far as I can see by your second patch QXL is just using exported > (that is not internal) functions. > Not that the idea of making them internal is bad but...

Am 27.09.19 um 18:31 schrieb Frediano Ziglio: >> The ttm_mem_io_* functions are actually internal to TTM and shouldn't be >> used in a driver. >> > As far as I can see by your second patch QXL is just using exported > (that is not internal) functions. > Not that the idea of making them internal is bad but...

Am 30.09.19 um 11:51 schrieb Frediano Ziglio: >> Am 27.09.19 um 18:31 schrieb Frediano Ziglio: >>>> The ttm_mem_io_* functions are actually internal to TTM and shouldn't be >>>> used in a driver. >>>> >>> As far as I can see by your second patch QXL is just using exported >>&...

This set of patches add some support for sector size >512. Currently it fixes extlinux, MBR for GPT and ext partitions. Other code is unaffected. This set of patches has been tested on a read Dell machine running a beta firmware.

...ild commit is 6859874b61d5ddaf5289e72ed2b2157739b72ca5) ------------------------- Added some patches: - tools-configure-qemu-for-spice-and-usbredir - libxl-Add-spice-vdagent-support-for-upstream-qemu - tools-firmware-seabios-packaged - tools: Improve make deb - vgabios-stdvga.bin custom build from Frediano - qemu-xen change for support other resolutions: hw/vga.c: # from Frediano patch - if ((val <= VBE_DISPI_MAX_XRES) && ((val & 7) == 0)) { + if ((val <= VBE_DISPI_MAX_XRES) && ((val & 1) == 0)) { - updated qemu upstream Config-mk: QEMU_UPSTREAM_REVISION ?= mas...

...ytes and also there are a lot of checks in different places (like in syslinux_check_bootsect). Currently I'm trying it to work using GPT and an ext3 partition. Anybody is working on similar issue or has some advice? Is there a way to emulate 4kb bios using any virtual environment? Regards Frediano

If EBIOS is detected for this drive it tries to read sector size and use it. If error or no EBIOS 512 is assumed. Buffer to read sector size if always allocated into the stack. CHS informations are not readed as not needed and same space not restoring %dl for drive number. Signed-off-by: Frediano Ziglio <frediano.ziglio at citrix.com> --- mbr/gptmbr.S | 42 +++++++++++++++++++++++++++++------------- 1 files changed, 29 insertions(+), 13 deletions(-) diff --git a/mbr/gptmbr.S b/mbr/gptmbr.S index b0c11b9..f0955b2 100644 --- a/mbr/gptmbr.S +++ b/mbr/gptmbr.S @@ -77,6 +77,12 @@ next:...

> > Am 27.09.19 um 18:31 schrieb Frediano Ziglio: > >> The ttm_mem_io_* functions are actually internal to TTM and shouldn't be > >> used in a driver. > >> > > As far as I can see by your second patch QXL is just using exported > > (that is not internal) functions. > > Not that the idea of m...

On Thu, Dec 06, 2018 at 07:53:10AM -0500, Frediano Ziglio wrote: > > > > On Thu, Dec 06, 2018 at 05:59:25AM -0500, Frediano Ziglio wrote: > > > > > > > > Just use qxl_num_crtc directly everywhere instead of using > > > > qdev->monitors_config->max_allowed. Drops pointless indirection > &gt...

From: Frediano Ziglio <fziglio at redhat.com> Instead of relaying on surface type use the actual placement. This allow to have different placement for a single type of surface. Signed-off-by: Frediano Ziglio <fziglio at redhat.com> [ kraxel: rebased, adapted to upstream changes ] Signed-off-by: Ge...