search for: implementat

Hi all, I was messing around with kexec and it seems to work just fine on KVM, but for Xen domU images, it doesn't work at all. Daniel, I saw some patches from you back in September 2012 for adding this support for Dom0, but they don't seem to have gone into the kernel (but other patches went into kexec-tools at that time.) You mention that domU support is "easy" after your

Hi all, I was messing around with kexec and it seems to work just fine on KVM, but for Xen domU images, it doesn't work at all. Daniel, I saw some patches from you back in September 2012 for adding this support for Dom0, but they don't seem to have gone into the kernel (but other patches went into kexec-tools at that time.) You mention that domU support is "easy" after your

Hi all, I was messing around with kexec and it seems to work just fine on KVM, but for Xen domU images, it doesn't work at all. Daniel, I saw some patches from you back in September 2012 for adding this support for Dom0, but they don't seem to have gone into the kernel (but other patches went into kexec-tools at that time.) You mention that domU support is "easy" after your

...VIRTIO_CONSOLE_PORT_READY control + message is sent to the host for that port so the host can let us know of + any additional configuration options set for that port. \end_layout \begin_layout Enumerate @@ -4822,6 +4862,13 @@ Because this is high importance and low bandwidth, the current Linux implementat ion polls for the buffer to be used, rather than waiting for an interrupt, simplifying the implementation significantly. + +\change_inserted 0 1271400345 + However, for generic serial ports with the O_NONBLOCK flag set, the polling + limitation is relaxed and the consumed buffers are freed upon...

...VIRTIO_CONSOLE_PORT_READY control + message is sent to the host for that port so the host can let us know of + any additional configuration options set for that port. \end_layout \begin_layout Enumerate @@ -4822,6 +4862,13 @@ Because this is high importance and low bandwidth, the current Linux implementat ion polls for the buffer to be used, rather than waiting for an interrupt, simplifying the implementation significantly. + +\change_inserted 0 1271400345 + However, for generic serial ports with the O_NONBLOCK flag set, the polling + limitation is relaxed and the consumed buffers are freed upon...

...m-dev at lists.llvm.org> Date: 08/24/2017 03:05 PM Subject: Re: [llvm-dev] [RFC] Enhance Partial Inliner by using a general outlining scheme for cold blocks On Thu, Aug 24, 2017 at 10:40 AM, Graham Yiu <gyiu at ca.ibm.com> wrote: Hi David, So I've began doing some implementation on the outlining portion of the code. Currently, I got the partial inliner to outline cold regions (single entry, single exit) of the code, based solely on the existence of ProfileSummaryInfo (ie. profiling data). However, I have some concerns on how this will co-exist with the existing...

...blocks >> ------------------------------ >> >> >> >> >> >> On Thu, Aug 24, 2017 at 10:40 AM, Graham Yiu <*gyiu at ca.ibm.com* >> <gyiu at ca.ibm.com>> wrote: >> >> Hi David, >> >> So I've began doing some implementation on the outlining portion of >> the code. Currently, I got the partial inliner to outline cold regions >> (single entry, single exit) of the code, based solely on the existence of >> ProfileSummaryInfo (ie. profiling data). However, I have some concerns on >> h...

Hi David, So I've began doing some implementation on the outlining portion of the code. Currently, I got the partial inliner to outline cold regions (single entry, single exit) of the code, based solely on the existence of ProfileSummaryInfo (ie. profiling data). However, I have some concerns on how this will co-exist with the existing code t...

...ot;true" usebox="none"> \begin_inset Text @@ -1181,6 +1277,88 @@ This allows for forwards and backwards compatibility: if the device is enhanced support, it will not see that feature bit in the Device Features field and can go into backwards compatibility mode (or, for poor implementations, set the FAILED Device Status bit). +\change_inserted 0 1265896046 + +\end_layout + +\begin_layout Subsubsection + +\change_inserted 0 1265896301 +Configuration/Queue Vectors +\end_layout + +\begin_layout Standard + +\change_inserted 0 1265908336 +When MSI-X capability is present and enabled...

...ot;true" usebox="none"> \begin_inset Text @@ -1181,6 +1277,88 @@ This allows for forwards and backwards compatibility: if the device is enhanced support, it will not see that feature bit in the Device Features field and can go into backwards compatibility mode (or, for poor implementations, set the FAILED Device Status bit). +\change_inserted 0 1265896046 + +\end_layout + +\begin_layout Subsubsection + +\change_inserted 0 1265896301 +Configuration/Queue Vectors +\end_layout + +\begin_layout Standard + +\change_inserted 0 1265908336 +When MSI-X capability is present and enabled...

...old, the minimum number of times the predecessor node has to be executed in order for an edge to be considered (confidence factor), and the minimum size of the region to be outlined (can use inlining cost analysis like we currently do) will require some level of tuning. Similar to the current implementation, we will attempt to inline the leftover (hot) parts of the code, and if for some reason we cannot then we discard the modified function and its outlined code. ### Code changes The current Partial Inlining code first clones the function of interest and looks for a single set of blocks to o...