similar to: [PATCH] fix typo in comment

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/misc/Makefile | 2 +- tools/misc/xencov_split | 191

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 @@

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 same sector). > > Unfortunately my company business required to

qxl has two modes: "native" (used by the drm driver) and "vga" (vga compatibility mode, typically used for boot display and firmware framebuffers). Accessing any vga ioport will switch the qxl device into vga mode. The qxl driver never does that, but other drivers accessing vga ports can trigger that too and therefore disturb qxl operation. So aquire the legacy vga ioports

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

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 >>> (that is not internal) functions. >>> Not that the

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

This is part of some patches to support sectors > 512. Currently I'm able to boot a Ubuntu kernel but seems that mboot is not working for some reason. This patch try to fix ADV size problem. Signed-off-by: Frediano Ziglio <frediano.ziglio at citrix.com> --- extlinux/main.c | 40 +++++++++++++++++++++++++++++++++++----- 1 files changed, 35 insertions(+), 5 deletions(-) diff

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 this comment is > a wrong statement. See the history of

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 this comment is > a wrong statement. See the history of

Hi, time ago I started doing support for 4k sector disk for syslinux. Patches worked for my cases (ext) and did not introduced regression 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)

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

I noted a possible problem restoring a machine. In xc_domain_restore (xc_domain_restore.c) if it''s not the last checkpoint we set O_NONBLOCK flag (search for fcntl) that we can call pagebuf_get or just load other pages (see following "goto loadpages;" line). Now we could ending up calling xc_tmem_restore/xc_tmem_restore_extra (xc_tmem.c) which call read_extract (xc_private.c)

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.

This is part of some patches to support sectors > 512. Currently I'm able to boot a Ubuntu kernel but seems that mboot is not working for some reason. This patch add a rdwr_bytes functions which remove the assumption in some places that sector is 512. This function is quite helpful if you are going to read/write a range of bytes to/from the stack without creating stack overflows for free.

Hi, I'm trying to get syslinux (extlinux actually) work with 4kb disks. I got a bios with 4kb support but seems that extlinux does not work at all. In extlinux/main.c SECTOR_SIZE and SECTOR_SHIFT are constants to 512 bytes 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

Hi, I installed samba on a large Active Directory. All is working, I use winbind in pam and everything is working. However sometime it just hang for a while (say 20 seconds) and then go without problems. Currently I increased "winbind cache time" to mitigate the problem. There are mainly two situation where this hang occur 1- login 2- ls -l 3- groups I tried to analyze the problem a

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.

OK, another prelease. This one is looking pretty good and the shortlog is appended below. Any testing that you can do would be greatly appreciated. In particular, Matt, could you try out this prerelease and see whether your disabled entries are no longer highlighted/selectable? If things stay looking good over the next few days we can hopefully cut a 4.06 final release at the weekend or early

This is part of some patches to support sectors > 512. Currently I'm able to boot a Ubuntu kernel but seems that mboot is not working for some reason. This patch try to fix first stage of extlinux bootloader but have some problems with ADV Signed-off-by: Frediano Ziglio <frediano.ziglio at citrix.com> --- dos/syslinux.c | 2 +- extlinux/main.c | 36